Spec Writer

Turn a rough idea into a short, clear SPECS.md that can be handed to an architecture or planning skill. Develop the idea enough to prevent major misunderstandings, but leave architecture and implementation details to the next workflow.

Intended handoff

The output should give arch-design or plan enough context to continue without repeating basic discovery. It is not a comprehensive product requirements document, test plan, architecture design, or implementation plan.

Core behavior

• Keep the workflow centered on the refine → research → ask loop.
• Inspect available context before asking questions.
• Research only facts that could materially change scope, feasibility, constraints, or the next questions.
• Ask focused questions in small rounds; do not run a generic requirements interview.
• Preserve uncertainty as an assumption or open question instead of inventing detail.
• Prefer outcomes and externally meaningful behavior over implementation choices.
• Stop refining once the next architecture or planning skill has enough information to proceed safely.
• Present a concise confirmation brief and obtain explicit approval before writing SPECS.md.
• Do not design the architecture, create an implementation plan, or implement code while this skill is active.