iterate-cr
/iterate-cr
Runs an iteration session that closes the last-mile gap between implemented Change Requests and the behaviour that was actually wanted. A specification is written before the code exists, so the delivered result is approximately right rather than exactly right. Closing that gap is an interactive loop the user drives: the user names what to try, the agent makes the change and reports what it observed, the user says what to try next. This skill records that loop as a roll-forward ledger at docs/cr/iterations/{YYYY-MM-DD}-{slug}.md, so the reasoning — including every approach a later change superseded — survives the session instead of evaporating with the agent's context. A ledger is not owned by one Change Request, so it has its own identity: the date it was opened and a short slug.
Usage:
| Invocation | Effect |
|---|---|
/iterate-cr |
Opens an exploration session with no Change Request (crs: empty) |
/iterate-cr CR-XXXX |
Opens a session against that Change Request, or resumes the one open ledger that covers it |
/iterate-cr CR-XXXX CR-YYYY |
Opens a session that covers every named Change Request, or resumes the one open ledger that covers them |
That is the whole surface. There is no close sub-command and no status sub-command, because neither would tell anyone anything the repository does not already hold. The ledger is a tracked document with a Git history: what the session has recorded is in the file, and when each entry landed is in git log. A session ends when the user stops iterating, which needs no ceremony to announce. Reconciling an accepted session into governance is a separate, deliberate step the user runs with /reconcile-cr.
Every named Change Request MUST resolve to an existing Change Request document. There is no implicit "current session".
The Roll-Forward Model
An iteration session moves in one direction, and the ledger records that motion rather than adjudicating it. Three properties define the model.