What problem does it solve?
Turning an accepted proposal into a buildable implementation spec is where projects quietly go wrong: specs get written against an imagined system, open questions get silently guessed, and one-way-door decisions lose their reasoning. This Skill enforces a gated, step-by-step workflow that produces a spec grounded in the actual codebase, with its trade-offs and unknowns recorded.
Core Features & Use Cases
- Mandatory execution order: Find the parent proposal, map the current system from real code, pass a scoping gate, then draft Goals, Non-goals, Design, Migration, and Test plan in a
specs/NNN-name/ folder.
- Decision Log and Open Questions: Append a Decision Log capturing one-way-door choices with reversal conditions, plus a live Open Questions backlog with closing evidence and deciders.
- Plan and task breakdown: Generate
plan.md and tasks.md from templates when the spec is greenlit, with dependency-ordered, independently verifiable tasks.
- Use Case: After a payment-retries proposal is accepted, ask the agent to scope the feature; it reads the existing billing code, proposes goals and non-goals for confirmation, then writes
specs/004-payment-retries/spec.md with a migration plan and decision log.
Quick Start
Ask the agent to turn the accepted proposal into an implementation spec for the feature you want to build.