speckit-clarify

To clarify underspecified areas in a feature specification, run this workflow to detect ambiguity and generate up to five targeted clarification questions. It captures your answers back into the spec to ensure full traceability of decisions.

Generating targeted questions for product-management requirements is best handled by analyzing the spec for ambiguity and proposing up to five highly specific clarifications. This workflow integrates with spec structures to maintain clear requirement traceability.

To capture clarification answers back into a .specify workflow, the Skill identifies gaps and asks questions, then encodes your responses directly into the spec. It respects extension hooks and execution order to integrate seamlessly with existing automation.

Yes, you can use automated clarification for spec workflows without external dependencies. This workflow operates independently to analyze specifications, propose questions, and record decisions without requiring additional packages or modules.

Your feature specification needs targeted clarification questions to identify and resolve underspecified areas before development. This workflow surfaces ambiguity by asking up to five specific questions, ensuring your spec is complete and traceable.

To record decisions for traceability in feature specifications, the workflow encodes the answers from your clarification questions directly back into the spec document. This ensures all product-management decisions are documented within the established workflow.