speckit-clarify

Identify underspecified areas in feature specs and encode clarification answers back into the spec.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-clarify-alidotcom2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/alidotcom2000/RSSFeedReader/tree/main/.github/skills/speckit-clarify
Command: npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-clarify-alidotcom2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguities, missing decisions, and vague requirements that cause rework during planning and implementation. This Skill systematically detects underspecified areas in a spec-kit feature spec and resolves them through targeted clarification questions before planning begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec against a taxonomy covering functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact questions one at a time, each with a recommended answer and multiple-choice or short-answer format. - Incremental Spec Updates: Writes each accepted answer into a ## Clarifications section and updates the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, scale targets, and acceptance criteria so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and ask clarification questions about any ambiguous requirements.

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 spec-kit feature specification?

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

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

Run clarification after /speckit-specify and before /speckit-plan. Clarifying first reduces downstream rework because the plan and tasks are generated from confirmed requirements rather than assumptions.

How many clarification questions does speckit-clarify ask?

It asks a maximum of 5 questions per session, prioritized by impact and uncertainty. Each question is multiple-choice or a short answer of five words or fewer, and you can stop early by saying done or proceed.

Does speckit-clarify work without a spec-kit project structure?

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

What happens to clarification answers after I respond?

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