speckit-clarify

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-clarify-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-clarify
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-clarify-wu-mao-chia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature specifications often contain ambiguity, 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, constraints, 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 applies it to the relevant spec sections with validation after every write. - Use Case: Before running /speckit-plan on a new feature, run this Skill to resolve open questions about security posture, data volume, and acceptance criteria so the plan is built on concrete decisions. ## Quick Start Ask the AI to run the speckit-clarify workflow on the current feature spec to find 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 on the active feature branch. 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 into a Clarifications section.

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

Run clarification after creating the spec with speckit-specify and before running speckit-plan. Resolving ambiguities first reduces downstream rework in planning, task decomposition, and acceptance test design.

Does speckit-clarify work without the .specify directory?▼

No. The workflow requires a spec-kit project structure with a .specify directory and an active feature spec. If the spec file is missing, it instructs you to run speckit-specify first rather than creating a new spec.

How many clarification questions can be asked per session?▼

A maximum of five questions per session. Each question must be answerable with a multiple-choice selection or a short answer of five words or fewer, and retries for the same question do not count toward the limit.

What happens to the answers after clarification questions?▼

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