skills.rest
luansilvadb
luansilvadbCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Identifies gaps in feature specs by generating up to 5 clarification questions and recording answers.

Updated Aug 23, 2026
Search Tags:#automation#workflow#documentation#specification#clarification#questions
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-clarify-luansilvadb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-clarify-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in a feature specification by generating up to 5 highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

  • Generates up to five targeted clarification questions per session to resolve ambiguity in requirements.
  • Inserts answers into a dedicated Clarifications section within the active spec for traceability.
  • Provides a session-based, date-stamped record that supports auditability and iterative planning.

Quick Start

Ask up to five targeted clarification questions and append each answer under a daily Clarifications session in the FEATURE_SPEC.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify underspecified areas in a feature specification?▼

To identify underspecified areas in a feature specification, you can generate up to five targeted clarification questions. This systematic approach resolves requirements ambiguity before planning begins.

How do I track specification clarifications for auditability?▼

Specification clarifications are tracked by inserting accepted answers into a dedicated Clarifications section within the active spec. This creates a session-based, date-stamped record for iterative auditability.

Can I use spec-kit workflow automation without a .specify/ directory?▼

No, spec-kit workflow automation requires a .specify/ directory. This directory drives the clarification process and provides the extension hooks necessary to update the active FEATURE_SPEC.

What is the best way to clarify specs before planning?▼

The best way to clarify specs before planning is using deterministic questioning. Generating a maximum of five targeted questions per session resolves ambiguity and encodes answers directly back into the specification.

Are there limitations to how many clarification questions I can generate per session?▼

Yes, there is a hard limit of five clarification questions per session. This deterministic constraint ensures focused requirement resolution and updates the specification only after each accepted answer.

Related Skills

Explore More Software Engineering Skills→
a2musa2mus

speckit-clarify

Detect and reduce ambiguities in feature specifications via structured clarification questions.

Community
Advanced
brianpunzalanbrianpunzalan

speckit-clarify

Clarify underspecified feature specs by asking targeted questions and applying answers.

Community
Advanced
kerolos-saaidkerolos-saaid

speckit-clarify

Identify underspecified areas in feature specs and generate up to five clarifying questions.

Community
Advanced
t-miura-024t-miura-024

mt-sdd-spec

Transform feature requests into structured specifications with multi-perspective review workflows.

Community
Advanced