speckit-clarify

Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-clarify-pieberrykinnie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/pieberrykinnie/hapa/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-clarify-pieberrykinnie

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 those gaps and resolves them through targeted questions before development begins. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories including functional scope, data model, non-functional requirements, edge cases, and terminology. - Interactive Questioning Loop: Asks up to 5 high-impact clarification 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 implementation planning on a new feature spec, use this Skill to resolve open questions about authentication, scale targets, and error handling so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to clarify the current feature spec, optionally naming specific areas such as security or data model to prioritize.

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 workflow on your spec file, which scans categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions. Each accepted answer is written back into the spec under a Clarifications section.

When should I run spec clarification in spec-kit?

Run clarification after creating the spec with speckit-specify and before running speckit-plan. Skipping it increases downstream rework risk, since unresolved ambiguities propagate into the implementation plan and tasks.

What project structure does spec clarification require?

It requires a spec-kit project with a .specify directory and an active feature spec located via the check-prerequisites script. If the spec file is missing, you must run speckit-specify first.

How many clarification questions can be asked per session?

A maximum of 5 questions per session, selected by impact and uncertainty across unresolved categories. Each question is either multiple-choice with a recommended option or a short answer constrained to 5 words or fewer.

Does clarification update the requirements checklist automatically?

Yes, if a checklists/requirements.md file exists in the feature directory, each checkbox item is re-evaluated against the updated spec. Only markers whose pass/fail state changed are toggled, and the completion report shows before and after counts.