Specification Clarification
Identify and resolve ambiguities in specifications through structured questioning. Use when specification has [NEEDS CLARIFICATION] markers, when user mentions unclear or ambiguous requirements, before creating implementation plans, or when planning reveals specification gaps.
npx skills add majiayu000/claude-skill-registry --skill clarify-specification --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
@.claude/shared-imports/constitution.md @.claude/shared-imports/memory-utils.md @.claude/templates/clarification-checklist.md # Specification Clarification ## Workflow Context **SDD Phase**: Phase 4 (Conditional - only if spec has ambiguities) **Command**: `/clarify` **Prerequisites**: `specs/$FEATURE/spec.md` with [NEEDS CLARIFICATION] markers **Creates**: Updated `specs/$FEATURE/spec.md` (resolved ambiguities) **Predecessor**: Phase 3 - `/feature` → `spec.md` **Successor**: Phase 5 - `/plan` → `plan.md` ### Phase Chain ``` Phase 1: /define-product → memory/product.md Phase 2: /generate-constitution → memory/constitution.md Phase 3: /feature → specs/$FEATURE/spec.md Phase 4: /clarify (if needed) → updated spec.md (YOU ARE HERE) + consults memory/ for existing patterns Phase 5: /plan → plan.md + research.md + data-model.md Phase 6: /tasks (auto) → tasks.md Phase 7: /audit (auto) → audit-report.md Phase 8: /implement → code + tests + verification ``` **$FEATURE format**: `NNN-feature-name` (e.g., `001-therapy-app`) **When to Use**: This phase is CONDITIONAL. Only invoked when: - spec.md contains [NEEDS CLARIFICATION] markers - User explicitly mentions unclear requirements - Planning
- Workflow Context
- Phase Chain
- Quick Reference
- Workflow Files
- Clarification Workflow (Overview)
- Phase 1: Load Specification and Detect Ambiguities
- Phase 2: Prioritize Clarification Questions
- Phase 3: Interactive Clarification
- Phase 4: Validation and Completion
- Phase 5: Re-Clarification (If Needed)
- Anti-Patterns to Avoid
- Example: E-Commerce Checkout Clarification
- Prerequisites
- Dependencies
What does the Specification Clarification skill do?
Identify and resolve ambiguities in specifications through structured questioning. Use when specification has [NEEDS CLARIFICATION] markers, when user mentions unclear or ambiguous requirements, before creating implementation plans, or when planning reveals specification gaps.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill clarify-specification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.