speckit-clarify

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-clarify-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-clarify
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-clarify-tjsasakifln

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 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 across 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 with recommended multiple-choice options or suggested short answers, capped at five 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 on a new feature, run this Skill to resolve open questions about security posture, data volume assumptions, and acceptance criteria 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 spec-kit feature specification?▼

Run the speckit-clarify workflow 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 five targeted questions and writes the answers back into the spec file.

When should I run spec clarification in a spec-driven workflow?▼

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

How many clarification questions does the workflow ask?▼

The workflow asks a maximum of five questions per session, presented one at a time. Each question is either multiple-choice with a recommended option or a short answer constrained to five words or fewer, prioritized by impact and uncertainty.

Does speckit-clarify require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory. It runs .specify/scripts/bash/check-prerequisites.sh to locate the feature spec and optionally reads .specify/memory/constitution.md and .specify/extensions.yml for hooks.

What happens to clarification answers after I respond?▼

Each accepted answer is appended as a bullet under a Clarifications session heading dated by day, and the relevant spec sections are updated immediately. The requirements checklist in checklists/requirements.md is then re-validated against the updated spec.