speckit-clarify

Identifies ambiguities in feature specifications and integrates clarification answers into spec files.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-clarify-marionoratorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/marionoratoRN/custom-speckit-flow/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/marionoratoRN/custom-speckit-flow --skill speckit-clarify-marionoratorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain vague requirements, missing decisions, and undefined edge cases that cause rework during implementation. This Skill systematically detects underspecified areas and resolves them through targeted questions before planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates specs across a taxonomy covering functional scope, data models, UX flows, non-functional requirements, integrations, and edge cases. - Interactive Questioning: Asks up to 5 prioritized multiple-choice or short-answer questions with recommended options based on best practices. - Incremental Spec Updates: Writes each accepted answer directly into the spec under a Clarifications section and updates affected requirement sections, then re-validates the spec quality checklist. - Use Case: After running /speckit-specify for a new feature, run this Skill to resolve open questions about authentication, data retention, and error handling before generating a technical plan. ## Quick Start Ask the assistant to clarify the current feature specification and resolve any ambiguous requirements before planning.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguities in a feature specification?▼

Run the clarify command after creating a spec with /speckit-specify. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes the answers back into the spec file.

When should I run spec clarification in the spec-kit workflow?▼

Run clarification after /speckit-specify and before /speckit-plan. Resolving ambiguities at this stage reduces downstream rework in technical planning, task decomposition, and acceptance test design.

How many clarification questions does the spec-kit clarify step ask?▼

It asks a maximum of 5 questions per session, prioritized by impact and uncertainty. Each question is either multiple-choice with a recommended option or a short answer constrained to five words or fewer.

Does speckit-clarify work without an existing feature spec?▼

No, it requires an existing feature spec created by /speckit-specify and a spec-kit project structure with a .specify directory. If the spec file is missing, it instructs you to run /speckit-specify first.

What happens to clarification answers in the spec file?▼

Each accepted answer is appended as a Q&A bullet under a Clarifications section and applied to the relevant spec sections, such as Functional Requirements or Success Criteria. The requirements checklist is then re-validated against the updated spec.