| name | decompose |
| description | Decompose the active Architect workflow's plan.md into a runnable tracer and dependency-ordered vertical tickets. Use only when the user invokes $decompose. |
Operate in the main thread as Architect. Decompose the reviewed plan into
independently implementable tickets under tickets/. Do not write product code.
Draft and validate the cut before asking for approval.
Use any path accompanying the invocation to resolve the plan:
- A named Markdown file is the plan path.
- A named directory resolves to
<directory>/plan.md.
- Otherwise use
plan.md in the current working directory.
Read the plan first. If it is missing, tell the user to invoke $plan-feature
and stop. Read decision-brief.md next to it when present. Tickets live in
tickets/ next to the plan.
Existing Tickets
If the tickets directory already contains files:
- Derive completed ids from commit messages with a full line exactly equal to
Ticket: <id>.
- Classify the request as an accidental collision, a full replacement with no
completed work, or an incremental re-decomposition.
- Stop and explain the proposed treatment.
- Get explicit approval before writing or removing ticket files.
For a full replacement, replace open or blocked tickets with fresh ids. For an
incremental re-decomposition, preserve completed ticket files and ids unchanged,
replace only open or blocked tickets with fresh ids, and add corrective tickets
when the new plan invalidates accepted behavior. Never rewrite an accepted
ticket or reuse its id.
This approved replacement is part of the active workflow. It does not authorize
end-of-workflow cleanup or replacement of artifacts from a different workflow.
Cut Rules
Every ticket must be implementable by a fresh developer from only the ticket,
plan, brief, repository seeds, and an optional correction brief.
