Plan Creation
Synthesize an implementation-ready plan rather than repeating discovery, architecture sparring, or research.
Workflow
- Confirm the brief, authoritative repository evidence, applicable instructions, output location, and whether writing a repository plan file is authorized.
- Identify only decisions whose absence changes the implementation path. Resolve them with the user or record a blocker; keep safe assumptions explicit.
- Use
architecture-refine for unresolved architecture decisions and technical-spike for blocking unfamiliar or version-sensitive behavior.
- Lock ownership boundaries, non-goals, compatibility, rollout order, validation gates, risks, and unresolved blockers.
- For behavior-changing work, name the authoritative contract, invariants and required progress, environmental assumptions, failure model, and material correctness claims. Map each claim to evidence; use
test-design when selecting verification methods is non-trivial and technical-spike when a high-consequence design may need unfamiliar model checking or proof.
- For work affecting long-running or distributed workloads, settle the source of truth and invariants; graceful and abrupt restart behavior; rolling replacement and mixed-version overlap; concurrent-replica ownership and coordination; duplicate, stale, or out-of-order work; partial dependency failure, retry exhaustion, ambiguous outcomes, and recovery. Require observable acceptance evidence for the applicable cases and omit the rest.
- Divide work into implementation-sized phases ordered by real dependencies.
- Give each phase a goal, concrete deliverables, dependencies, steps, acceptance evidence, and structural traps to avoid.
- Reread the plan for hidden assumptions, missing prerequisites, contradictory acceptance criteria, failure and recovery gaps, and duplicate ownership.
Use the repository's established plan format. Omit empty ceremony. Name concrete subsystems, files, interfaces, migrations, UI surfaces, or test layers only where they remove implementation ambiguity.
Do not implement, validate, commit, push, or release. Keep a local behavior-preserving structural plan proportionate to its actual risk.
Finish when implementation-changing decisions are settled or explicit blockers, phases are dependency-ordered, and every phase has observable acceptance evidence.
1---2name: plan-create3description: Create a final implementation-ready plan from a user brief, settled decisions, and repository evidence. Use when work needs ordered phases, concrete deliverables, dependencies, risks, and validation before coding.4---56# Plan Creation78Synthesize an implementation-ready plan rather than repeating discovery, architecture sparring, or research.910## Workflow11121. Confirm the brief, authoritative repository evidence, applicable instructions, output location, and whether writing a repository plan file is authorized.132. Identify only decisions whose absence changes the implementation path. Resolve them with the user or record a blocker; keep safe assumptions explicit.143. Use `architecture-refine` for unresolved architecture decisions and `technical-spike` for blocking unfamiliar or version-sensitive behavior.154. Lock ownership boundaries, non-goals, compatibility, rollout order, validation gates, risks, and unresolved blockers.165. For behavior-changing work, name the authoritative contract, invariants and required progress, environmental assumptions, failure model, and material correctness claims. Map each claim to evidence; use `test-design` when selecting verification methods is non-trivial and `technical-spike` when a high-consequence design may need unfamiliar model checking or proof.176. For work affecting long-running or distributed workloads, settle the source of truth and invariants; graceful and abrupt restart behavior; rolling replacement and mixed-version overlap; concurrent-replica ownership and coordination; duplicate, stale, or out-of-order work; partial dependency failure, retry exhaustion, ambiguous outcomes, and recovery. Require observable acceptance evidence for the applicable cases and omit the rest.187. Divide work into implementation-sized phases ordered by real dependencies.198. Give each phase a goal, concrete deliverables, dependencies, steps, acceptance evidence, and structural traps to avoid.209. Reread the plan for hidden assumptions, missing prerequisites, contradictory acceptance criteria, failure and recovery gaps, and duplicate ownership.2122Use the repository's established plan format. Omit empty ceremony. Name concrete subsystems, files, interfaces, migrations, UI surfaces, or test layers only where they remove implementation ambiguity.2324Do not implement, validate, commit, push, or release. Keep a local behavior-preserving structural plan proportionate to its actual risk.2526Finish when implementation-changing decisions are settled or explicit blockers, phases are dependency-ordered, and every phase has observable acceptance evidence.
yarlson