refine-specification

To refine a draft specification, provide your draft file path or paste the content to trigger domain-by-domain clarifying questions across scope, users, data, integration, and non-functional aspects. This generates a refined Markdown specification saved as [feature-name]-specification.md in your feature specs directory.

For Rails feature planning requirements analysis, ask guided clarifying questions covering scope boundaries, user roles, data models, external integration points, and non-functional requirements. Follow-up questions resolve ambiguities and surface risks to produce an implementation-ready specification.

Yes, this specification clarification workflow applies to Rails and web app feature work, covering scope, users, data, integration, and non-functional domains. It uses structured outputs and follow-up questions to finalize a refined specification ready for planning.

Yes, you can generate a Markdown specification file from a rough feature draft. The workflow identifies gaps in your draft, asks targeted clarifying questions, and saves the final refined specification as a Markdown file in your project's feature specs directory.

The best way to identify gaps in a feature specification draft is applying domain-by-domain analysis across scope, users, data, integration, and non-functional aspects. This approach generates targeted clarifying questions and follow-ups to surface risks and resolve ambiguities.

You should not use a clarifying questions workflow for feature planning if your draft specification is already implementation-ready, lacks ambiguities, or requires no domain analysis across scope, users, data, integration, and non-functional requirements.