{{command_prefix}}new-cycle
The cycle is the hierarchical unit above individual pipeline runs: Cycle > Pipeline run > Wave > Task. Each cycle has a goal, tracks its own decisions, and can span many pipeline runs. {{command_prefix}}complete-cycle closes the cycle once goals are met and a retrospective is captured.
Steps
-
Read
.design/STATE.md. Ifcycle:field is populated and nocompleteflag, ask: "Cycle is active. End it first with{{command_prefix}}complete-cycle?" Abort if user declines. -
If no goal was passed as an argument, ask (AskUserQuestion): "What is the goal for this design cycle? (e.g., 'Redesign the checkout flow', 'Improve dashboard accessibility')"
-
Generate cycle ID: read
.design/CYCLES.mdif present, find the maxcycle-N, increment. If CYCLES.md is missing, start atcycle-1. -
Update
.design/STATE.mdfrontmatter: setcycle: cycle-N. -
Create or append to
.design/CYCLES.md:markdown## cycle-N: <goal> **Started**: <date> **Status**: active **Goal**: <goal> **Pipeline runs**: 0 **Decisions made**: 0 -
Reset the
<decisions>section in STATE.md for the new cycle. Preserve prior decisions by prepending a comment marker<!-- prior cycle decisions archived in CYCLES.md -->. -
Print: "Cycle cycle-N started. Run
@get-design-done briefor@get-design-done exploreto begin."
Do Not
- Do not archive prior artifacts here - that's
{{command_prefix}}complete-cycle. - Do not overwrite the existing CYCLES.md - append only.


