wa:spec-questions

Triage specification gaps by auditing FRD.md and DISCOVERY.md files to identify missing scope coverage, untestable acceptance criteria, and conflicts, then categorize each gap as a blocking or non-blocking open question.

Specification gap analysis is the process of reviewing requirements documents to find ambiguous criteria, missing error states, and scope conflicts before development begins, ensuring stakeholder alignment on feature delivery.

Generate an open questions table by analyzing acceptance criteria for testability and completeness, then appending a canonical list of decision-ready blocking and non-blocking questions directly into the feature's FRD.md.

Yes, you can control requirements triage depth by adjusting the development rigor mode, which varies the audit exhaustiveness from surfacing only blockers to performing a full specification gap analysis.

You need defined feature scope, acceptance criteria, and discovery requirements structured within FRD.md and DISCOVERY.md files mapped to a specific feature slug to execute the stage-gated analysis.

Specification gaps are marked as non-blocking questions when they involve missing error states or ambiguous requirements that do not halt feature delivery, allowing stakeholders to address them asynchronously.