speckit-clarify

To clarify underspecified points in a feature specification, use a structured Q&A workflow that prompts up to five targeted clarification questions and appends confirmed answers directly into the spec.

The best way to identify gaps in functional requirements and data models is to detect missing details across functional scope and UX flow, then generate prioritized questions to resolve them.

You can update a feature spec with testable success criteria by running a clarification session that encodes answers back into the spec, updating rationale in the appropriate sections with measurable targets.

Yes, you can track specification clarifications for audit purposes because the workflow maintains a one-session archive per day, providing an auditable trail of decisions made during the Q&A loop.

Yes, you need a valid feature spec present at the spec path before starting a clarification session, as the workflow relies on frontmatter-defined name and description fields for discovery and updates.

The clarification workflow limits sessions to five questions to drive a focused, one-session Q&A loop that efficiently resolves underspecified decision points without overwhelming the collaborator.