speckit-clarify

Identifies underspecified areas in feature specs and records targeted clarification answers.

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

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 high-impact clarification questions, and writes the answers directly back into the spec file. ## 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: Presents one question at a time (multiple-choice or short answer) with a recommended option and reasoning, capped at 5 questions per session. - Incremental Spec Updates: Appends each accepted answer to a ## Clarifications session section and updates the relevant spec sections, then re-validates the requirements checklist. - Use Case: Before running /speckit-plan, a developer runs this Skill on a new feature spec to resolve open questions about authentication, scale targets, and error handling so the plan is built on firm decisions. ## Quick Start Ask the assistant to run the speckit-clarify skill to review the current feature spec and resolve its 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 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 file.

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 either multiple-choice with a recommended option or a short answer constrained to 5 words or fewer.

What project structure does speckit-clarify require?▼

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.

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

Run it after /speckit-specify and before /speckit-plan. Skipping clarification is allowed for exploratory spikes, but the skill warns that downstream rework risk increases.

Does speckit-clarify update the requirements checklist automatically?▼

Yes. If FEATURE_DIR/checklists/requirements.md exists, it re-evaluates each checkbox item against the updated spec, toggles only markers whose state changed, and reports newly passing items, regressions, and remaining gaps.