specification-phase

To turn natural language feature requests into structured specifications, this Skill orchestrates a specification phase that parses text ideas, classifies features with flags like HAS_UI, and generates a spec.md file with requirements and clarifications.

You can classify product features for requirements gathering by applying automated flags such as IS_IMPROVEMENT, HAS_METRICS, and HAS_DEPLOYMENT_IMPACT, which helps determine research depth and structure the specification workflow.

The best way to document feature requests for development planning is to generate a structured spec.md file, which details success criteria, necessary clarifications, and feature classifications to reduce ambiguity before development begins.

Yes, you can use this specification workflow for improving existing product features because it automatically applies the IS_IMPROVEMENT flag during feature classification to tailor the requirements gathering process.

The specification phase generates up to three critical clarifications for a new feature, applying informed guesses for defaults to ensure the structured specification is actionable without excessive back-and-forth.