speckit-clarify

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

Updated Jan 28, 2024
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-clarify-thiago-cruz-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Thiago-Cruz-eng/KrockSide/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill speckit-clarify-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguous requirements, missing edge cases, and vague non-functional criteria that cause rework during planning and implementation. This Skill systematically scans a spec-kit feature spec, asks up to five 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 attributes, integrations, edge cases, constraints, and terminology. - Interactive Questioning Loop: Presents one question at a time with a recommended multiple-choice option or suggested short answer, capped at five questions per session. - Incremental Spec Updates: Appends each accepted answer to a ## Clarifications session section and applies it to the relevant spec section, saving after every write. - Use Case: Before running /speckit-plan on a new feature branch, run this Skill to resolve open questions about security posture, scale assumptions, and acceptance criteria so the implementation 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 its most critical ambiguities.

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 workflow on the active feature branch. It scans the spec against a coverage taxonomy, asks up to five targeted questions one at a time, and writes each accepted answer into a Clarifications section of the spec file.

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

Run clarification after /speckit-specify and before /speckit-plan. Skipping it is allowed for exploratory spikes, but the workflow warns that downstream rework risk increases when ambiguities reach the planning phase.

What project structure does speckit-clarify require?▼

It requires a spec-kit project with a .specify directory and the check-prerequisites PowerShell script, which returns the FEATURE_DIR and FEATURE_SPEC paths as JSON. If the spec file is missing, it instructs you to run /speckit-specify first.

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each question is either multiple-choice with two to five options or a short answer constrained to five words or fewer, and retries on the same question do not count against the quota.

What happens if no ambiguities are found in the spec?▼

The workflow reports that no critical ambiguities were detected, outputs a compact coverage summary showing all taxonomy categories as Clear, and suggests proceeding to the planning step.