skills.rest
vutrunghieu23-2
vutrunghieu23-2COMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Resolve ambiguous feature specs through structured clarification in spec-kit projects.

Updated Aug 23, 2026
Search Tags:#specification#requirements#clarification#ambiguity-resolution#coverage-mapping#question-workflow
One-click install
npx skills add https://github.com/vutrunghieu23-2/ts2mp4 --skill speckit-clarify-vutrunghieu23-2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/vutrunghieu23-2/ts2mp4/tree/main/.agent/skills/speckit-clarify
Command: npx skills add https://github.com/vutrunghieu23-2/ts2mp4 --skill speckit-clarify-vutrunghieu23-2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When feature requirements are underspecified it risks misaligned implementations and wasted effort, so this Skill surfaces missing decisions before the planning stage.

Core Features & Use Cases

  • Coverage Taxonomy Scan: Evaluates functional, domain, interaction, non-functional, integration, edge-case, and terminology categories for Partial or Missing status before acting.
  • Constrained Question Workflow: Builds and sequences up to five high-impact, short-form questions that can update the spec in natural language and logs answers.
  • Spec Integration: Ensures answers are recorded under a dated Clarifications section and updates the most relevant spec section, keeping the doc actionable for downstream planning.

Quick Start

Clarify the active feature specification before planning begins.

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ambiguous feature specifications before starting the planning phase?▼

To resolve ambiguous feature specifications, this Skill scans coverage categories like functional, domain, and edge-case requirements to identify gaps, then generates up to five high-impact questions to interrogate underspecified specs before planning begins.

What is a coverage taxonomy scan for requirement clarification?▼

A coverage taxonomy scan evaluates functional, domain, interaction, non-functional, integration, edge-case, and terminology categories within a spec to identify Partial or Missing status, ensuring comprehensive requirement interrogation before acting.

How do I integrate clarification answers into a feature spec document?▼

To integrate clarification answers, record them under a dated Clarifications section and update the most relevant spec section, ensuring the feature spec document remains actionable for downstream planning activities.

Does requirement clarification work with spec-kit projects that use .specify directories?▼

Yes, structured requirement clarification applies specifically to spec-kit projects containing .specify directories, enabling it to interrogate underspecified requirements and log answers directly within the existing project structure.

What is the maximum number of questions generated to clarify a specification?▼

The maximum number of questions generated to clarify a specification is five, built and sequenced as high-impact, short-form queries that update the spec in natural language while logging answers efficiently.

Related Skills

Explore More Product & Management Skills→
niisaraniisara

speckit-clarify

Identify underspecified areas in feature specifications and generate targeted questions.

Community
Advanced
GarethJBGarethJB

speckit-clarify

Identify underspecified areas in feature specs and encode clarifications into the document.

Community
Advanced
SorinSSorinS

speckit-plan

Automate Spec-Driven Development planning phases and generate design artifacts.

Community
Advanced
sbonocsbonoc

blueprint-sdd-step01-intake

Automate initial scoping and documentation for SDD software projects.

Community
Intermediate