skills.rest
code-dot-org
code-dot-orgOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-clarify

Identify underspecified decisions in feature specs and record answers into a Clarifications section.

1|Updated Oct 21, 2025
Search Tags:#planning#specification#requirements#interactive#docs#acceptance-criteria#clarify
One-click install
npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-clarify-code-dot-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/code-dot-org/marketing-sites/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-clarify-code-dot-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in a feature specification by guiding an interactive session that yields up to five targeted clarifications and encodes the answers back into the spec.

Core Features & Use Cases

  • Up to five focused clarification questions to surface missing decisions in a feature spec.
  • Automatic integration of accepted answers into a structured Clarifications section in the spec, organized by session date.
  • Supports post-clarification validation with explicit success criteria and placement into functional, data, UX, and non-functional sections.

Quick Start

Run the speckit-clarify workflow against the active spec to generate and apply up to five targeted clarifications.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify missing requirements in a feature specification?▼

You identify missing requirements by running an interactive clarification session that generates up to five targeted questions to resolve underspecified functional, UX, data, and non-functional decisions in your spec.

How do I add acceptance criteria to a feature spec after clarifying requirements?▼

You add acceptance criteria by enforcing concrete success metrics during the clarification session, then placing validated answers into the functional, data, UX, and non-functional sections of the active specification.

Does speckit-clarify require a specific workspace format?▼

Yes, speckit-clarify requires a .specify workspace. It reads your active feature specification from this environment and integrates resolved answers directly back into the document.

How are clarified specification decisions recorded back into the document?▼

Clarified specification decisions are recorded into a structured Clarifications section organized by today's session date, integrating accepted answers directly into the active spec to minimize downstream rework.

What is the maximum number of clarification questions generated per session?▼

The maximum number of clarification questions generated per session is five. This strict limit ensures focused resolution of underspecified areas without overwhelming the feature specification review.

Related Skills

Explore More Product & Management Skills→
tomlmtomlm

speckit-clarify

Generate targeted clarification questions for underspecified feature specifications and record answers.

Community
Advanced
racciolyraccioly

speckit-clarify

Detect ambiguities in feature specs and generate prioritized clarifying questions.

Community
Advanced
kerolos-saaidkerolos-saaid

speckit-clarify

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

Community
Advanced
j7-devj7-dev
1

clarify-loop

Guide users through sequential questions to clarify and specify requirements.

Community
Intermediate