Spec Generator

Produce Symphony-style technical specifications optimized for agentic consumption. Specs use imperative voice, concrete values, RFC 2119 keywords, tables, pseudocode, and implementation checklists — no filler.

Workflow

1. Call EnterPlanMode immediately upon invocation
2. Use plan mode's built-in workflow to explore the codebase (if one exists) and gather requirements via AskUserQuestion
3. Write the spec as the plan file content, using the format and sections defined below
4. The user iterates by rejecting ExitPlanMode — revise the spec and re-propose
5. After exiting plan mode, copy the plan file content to ./SPEC.md in the working directory
   • If SPEC.md already exists, use SPEC-<name>.md where <name> is a short kebab-case identifier
6. Inform the user of the output file path

Question Categories

During plan mode, use AskUserQuestion to gather requirements. Focus on these categories as relevant — skip categories that are obvious or not applicable:

• What: Core functionality, inputs, outputs, key operations