speckit-clarify

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

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-clarify-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-clarify-alkampfergit

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 across a taxonomy of categories including functional scope, data model, non-functional requirements, edge cases, and terminology, marking each as Clear, Partial, or Missing. - Interactive Questioning Loop: Asks up to 5 high-impact clarification questions one at a time, each with a recommended option or suggested answer, then encodes accepted answers directly into the spec under a Clarifications section. - Checklist Re-validation: Re-evaluates the spec quality checklist after updates, reporting newly passing items, regressions, and remaining gaps. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, scale assumptions, and acceptance criteria so downstream planning proceeds on a solid spec. ## Quick Start Ask the assistant to clarify the current feature spec, optionally naming specific areas to focus on, and answer the questions it presents.

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 in a project with a .specify directory. It scans the active feature 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.

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 risk in planning, task decomposition, and acceptance test design.

How many clarification questions does the skill ask per session?▼

It asks a maximum of 5 questions per session, selected 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 require a specific project structure?▼

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

What happens to the requirements checklist after clarification?▼

If FEATURE_DIR/checklists/requirements.md exists, the skill re-evaluates each checkbox against the updated spec, toggling only markers whose state changed, and reports newly passing items, regressions, and items still unchecked.