specification-phase

Transform feature requests into structured specifications by defining scope, measurable success criteria, and classifications. This Skill converts natural language ideas into detailed specs with artifacts including spec documents, notes, visuals, and workflow state, ready for roadmap integration and team implementation.

Include classification flags (HAS_UI, IS_IMPROVEMENT, HAS_METRICS, HAS_DEPLOYMENT_IMPACT), measurable success criteria, informed-guess defaults for technical decisions, and clear scope boundaries. The Skill generates spec.md, NOTES.md, visuals documentation, and workflow-state.yaml to ensure nothing is ambiguous.

Specifications automatically link to existing roadmap entries and update their status during the specification phase. This maintains project alignment, prevents duplicate work, and ensures new features fit within planned development cycles and resource constraints.

Yes. Define quantifiable metrics and measurement methods for each requirement during specification. This ensures objective validation later and prevents scope creep by establishing clear, testable success criteria upfront.

Early classification (HAS_UI, IS_IMPROVEMENT, HAS_METRICS, HAS_DEPLOYMENT_IMPACT) guides downstream workflow, artifact generation, and team allocation. It prevents misinterpretations and reduces rework by making technical implications explicit before development begins.

Informed-guess strategy applies reasonable defaults for non-critical technical decisions, minimizing clarification overhead. This accelerates the specification process by resolving low-stakes ambiguities automatically rather than blocking on perfect clarity.