speckit-clarify

Identify underspecified areas in a feature specification and integrate clarifications.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-clarify-kamalsroor1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/kamalsroor1/nest-scaffolding-crud-manager/tree/main/.agent/skills/speckit-clarify
Command: npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-clarify-kamalsroor1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams detect underspecified areas and decision gaps in a feature specification and prevents downstream rework by eliciting concise clarifications and encoding them back into the spec file.

Core Features & Use Cases

  • Detects ambiguity and coverage gaps across functional scope, data model, UX flows, non-functional requirements, integrations, edge cases, constraints, and terminology.
  • Generates a prioritized queue of up to five targeted, answer-constrained clarification questions and runs a sequential interactive loop that records accepted answers.
  • Integrates answers directly into the FEATURE_SPEC, preserves heading hierarchy, creates a dated Clarifications session, runs pre/post extension hooks when present, and performs validation on each write.
  • Use case examples: a product manager refining acceptance criteria before planning, an engineer resolving data-model uncertainties before implementation, or a reviewer ensuring testable success criteria.

Quick Start

Use speckit-clarify to scan the active feature spec, ask up to five targeted clarification questions, and integrate accepted answers back into the feature spec file.

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 feature specification before implementation?

Use the speckit-clarify Skill to identify ambiguities in a feature specification, ask up to five targeted clarification questions interactively, and record accepted answers directly back into the spec file.

What types of coverage gaps can be detected in a feature spec?

Spec clarification detects coverage gaps across functional scope, data models, UX flows, non-functional requirements, integrations, edge cases, constraints, and terminology to resolve decision gaps before implementation.

How do I run spec clarification using a spec-kit directory structure?

Running spec clarification requires repository access to the feature spec file and permission to execute the .specify check-prerequisites script to extract the FEATURE_DIR and FEATURE_SPEC paths.

Does spec clarification support integrating answers into an existing feature spec file?

Yes, spec clarification integrates answers into the feature spec file by preserving heading hierarchy, creating a dated Clarifications session, running pre/post extension hooks, and performing validation on each write.

How many clarification questions are generated for a feature spec?

A prioritized queue of up to five targeted, answer-constrained clarification questions is generated for a feature spec, running a sequential interactive loop that records accepted answers.

When should I not use automated spec clarification for requirements validation?

Avoid automated spec clarification when you lack repository access to the feature spec file or cannot run the .specify check-prerequisites script required to extract the FEATURE_DIR and FEATURE_SPEC.