Verified:GitHub

wa:spec-questions

Identify and triage specification gaps as blocking or non-blocking questions.

Updated Mar 26, 2026

Search Tags:#documentation #specification #acceptance criteria #stakeholder alignment #FRD #open questions #requirements triage

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-spec-questions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:spec-questions
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/spec-questions
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-spec-questions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams turn scattered requirements and acceptance criteria into an actionable list of open questions, clearly marked as blocking or non-blocking.

Core Features & Use Cases

Specification gap analysis: Identifies missing scope coverage, ambiguous requirements, untestable acceptance criteria, conflicts across documents, and missing error states.
Mode-based triage depth: Uses development rigor to vary how exhaustive the audit is (from blockers-only to full audit).
Decision-ready documentation: Writes a canonical Open Questions table into the feature’s FRD.md for stakeholder follow-up.

Quick Start

Run /spec-questions with a feature description to generate and triage the open questions, then append them to docs/{feature}/FRD.md.

Frequently Asked Questions about wa:spec-questions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I triage specification gaps in my feature requirements?▼

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.

What is specification gap analysis for feature delivery?▼

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.

How do I generate an open questions table from acceptance criteria?▼

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.

Can I control the depth of my requirements triage audit?▼

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.

What do I need to run specification gap analysis on my feature docs?▼

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.

Why are some specification gaps marked as non-blocking questions?▼

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.