speckit-clarify

Spec clarification involves identifying ambiguities in feature requirements and generating up to 5 targeted questions. This workflow surfaces underspecified areas before planning, reducing early project risk by encoding accepted answers directly back into the feature spec.

Yes, spec clarification requires an existing .specify/ directory structure. The workflow operates exclusively on feature specs managed within this .specify/ workflow, automatically encoding accepted answers into the spec file with timestamped session entries.

The workflow updates feature requirements by appending a '## Clarifications' section to the spec file. Each accepted answer is encoded under a '### Session YYYY-MM-DD' entry, keeping documentation synchronized with the latest clarifications.

The maximum number of clarification questions generated is 5. The workflow guides users through answering these targeted questions to finalize clarifications, ensuring the process remains concise and high-impact before proceeding to planning.

Run the clarification workflow before proceeding to the planning phase. It identifies underspecified areas in your current feature spec, enabling early risk reduction by surfacing ambiguities and encoding the answers back into the .specify/ documentation.