speckit-clarify

Detects underspecified areas in feature specs and integrates clarification answers into the spec file.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-clarify-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-clarify-luandopke

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 scans a spec-kit feature spec, asks up to 5 targeted clarification questions, and writes the accepted answers directly back into the spec. ## Core Features & Use Cases - Structured Ambiguity Scan: Evaluates the spec across a taxonomy of categories including functional scope, data model, UX flow, non-functional requirements, integrations, and edge cases. - Interactive Questioning Loop: Presents one question at a time with recommended multiple-choice options or suggested short answers, capped at 5 questions per session. - Incremental Spec Integration: Appends each accepted answer to 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 authentication, data constraints, or error handling so the plan is built on confirmed decisions. ## Quick Start Ask the assistant to run the speckit-clarify workflow on the current feature spec to identify and resolve ambiguities 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 speckit-clarify workflow on the active feature spec. It scans the spec across categories like functional scope, data model, and edge cases, then asks up to 5 targeted questions and writes accepted answers back into the spec file.

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

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

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts like check-prerequisites.sh and the feature spec file. If the spec is missing, it instructs you to run /speckit-specify first.

How many clarification questions can be asked per session?▼

A maximum of 5 questions per session. Each question is either multiple-choice with 2-5 options or a short answer constrained to 5 words or fewer, prioritized by impact and uncertainty.

What happens to clarification answers after I respond?▼

Each accepted answer is appended as a bullet under a Clarifications section with a dated session heading, then applied to the relevant spec sections such as Functional Requirements or Data Model. The spec file is saved after each integration.

Why does the requirements checklist change after clarification?▼

If FEATURE_DIR/checklists/requirements.md exists, the Skill re-evaluates each checkbox item against the updated spec and toggles markers only when pass/fail state changes. The completion report shows before and after pass counts.