How do I install the Spec Clarify skill?

Run npx skillmds add xfstudio/spec-clarify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Clarify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Clarify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Clarify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Clarify?

xfstudio (@xfstudio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Clarify by xfstudio — Agent Skill

Name: Spec Clarify
Rating: 4.2 (5 reviews)
Author: xfstudio

Spec Clarify

Identify underspecified areas in a feature spec by asking up to 5 targeted clarification questions and encoding answers into the spec. Use when user says "/spec-clarify", "clarify the spec", or after /spec-specify to reduce ambiguity before /spec-plan.

xfstudio 9c3f2cd 2.0 KB Updated Sep 10, 2026

File contents

Spec-Clarify

Reduce ambiguity in specifications through targeted questioning.

Prerequisites: Feature spec must exist (run /spec-specify first).

Workflow

Initialize - Run .specify/scripts/bash/check-prerequisites.sh --json --paths-only
Load spec - Read spec.md
Scan ambiguity - Analyze coverage taxonomy
Generate questions - Max 5, prioritized by impact
Question loop - Present ONE at a time with recommendation
Integrate answers - Update spec after each answer
Report - Output summary and next steps

Ambiguity Taxonomy

Categories to scan (mark Clear/Partial/Missing):

Category	Check For
Functional Scope	User goals, out-of-scope, personas
Data Model	Entities, relationships, constraints
UX Flow	Journeys, error states, accessibility
Non-Functional	Performance, security, observability
Integration	External APIs, formats, versioning
Edge Cases	Negative scenarios, rate limits

Question Format

Multiple Choice:

**Recommended:** Option A - <reasoning>

| Option | Description |
|--------|-------------|
| A | Option A |
| B | Option B |
| Short | Custom answer (<=5 words) |

Short Answer:

**Suggested:** <answer> - <reasoning>
Format: <=5 words. Say "yes" or provide your own.

Integration Rules

After each answer:

Add ## Clarifications section if missing
Add ### Session YYYY-MM-DD subheading
Append: - Q: <question> → A: <answer>
Update relevant spec section
Save immediately

Constraints

Max 5 questions asked
Max 10 questions total across session
Respect "done", "stop", "proceed" signals

Next Steps

After /spec-clarify:

/spec-plan - Create technical plan

---name: spec-clarifydescription: Identify underspecified areas in a feature spec by asking up to 5 targeted clarification questions and encoding answers into the spec. Use when user says "/spec-clarify", "clarify the spec", or after /spec-specify to reduce ambiguity before /spec-plan.---# Spec-ClarifyReduce ambiguity in specifications through targeted questioning.**Prerequisites**: Feature spec must exist (run `/spec-specify` first).## Workflow1. **Initialize** - Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only`2. **Load spec** - Read spec.md3. **Scan ambiguity** - Analyze coverage taxonomy4. **Generate questions** - Max 5, prioritized by impact5. **Question loop** - Present ONE at a time with recommendation6. **Integrate answers** - Update spec after each answer7. **Report** - Output summary and next steps## Ambiguity TaxonomyCategories to scan (mark Clear/Partial/Missing):| Category | Check For ||----------|-----------|| Functional Scope | User goals, out-of-scope, personas || Data Model | Entities, relationships, constraints || UX Flow | Journeys, error states, accessibility || Non-Functional | Performance, security, observability || Integration | External APIs, formats, versioning || Edge Cases | Negative scenarios, rate limits |## Question Format**Multiple Choice:**```markdown**Recommended:** Option A - <reasoning>| Option | Description ||--------|-------------|| A | Option A || B | Option B || Short | Custom answer (<=5 words) |```**Short Answer:**```markdown**Suggested:** <answer> - <reasoning>Format: <=5 words. Say "yes" or provide your own.```## Integration RulesAfter each answer:1. Add `## Clarifications` section if missing2. Add `### Session YYYY-MM-DD` subheading3. Append: `- Q: <question> → A: <answer>`4. Update relevant spec section5. Save immediately## Constraints- Max 5 questions asked- Max 10 questions total across session- Respect "done", "stop", "proceed" signals## Next StepsAfter `/spec-clarify`:- `/spec-plan` - Create technical plan

Frequently asked questions