skills.rest
GarethJB
GarethJBCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

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

Updated Apr 13, 2026
Search Tags:#automation#workflow#requirements#engineering#spec#clarify
One-click install
npx skills add https://github.com/GarethJB/workflow-plugin --skill speckit-clarify-garethjb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/GarethJB/workflow-plugin/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill speckit-clarify-garethjb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec by prompting up to five targeted clarification questions and encoding answers back into the spec to reduce rework and misaligned expectations.

Core Features & Use Cases

  • Interactive clarification sessions surface high-impact ambiguities across functional, data, UX, and non-functional domains.
  • Session-based tracking automatically adds a Clarifications section to the active spec and records each Q&A for traceability.
  • Limits clarifications to five questions, prioritizing questions by impact and potential downstream rework risk.
  • Integrates with pre- and post-clarification hooks and extensions to align with existing spec-kit workflows.

Quick Start

Run /speckit.clarify to start a clarification session against your current spec and begin answering targeted questions.

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?▼

You clarify feature specifications by running an interactive session that prompts up to five targeted questions across functional, data, UX, and non-functional domains to surface high-impact ambiguities and reduce downstream rework.

What is the best way to track clarification questions for a spec document?▼

The best way to track spec clarifications is using session-based tracking that automatically adds a Clarifications section to the active spec document, recording each question and answer to maintain traceability for downstream planning.

How many clarification questions can I generate per spec session?▼

You can generate up to five clarification questions per spec session, with the system automatically prioritizing questions by impact and potential downstream rework risk to ensure focused requirements gathering.

Can I encode clarification answers directly back into the spec project structure?▼

Yes, you can encode clarification answers directly back into the spec project structure, automatically adding a dedicated section to the active spec document to record decisions and align expectations for future engineering work.

Does the spec clarification process integrate with existing workflow extensions?▼

Yes, the spec clarification process supports integration with pre- and post-clarification hooks and extensions, allowing you to align targeted question sessions with existing spec-kit workflows and automation processes.

Related Skills

Explore More Software Engineering Skills→
ztwosoneztwosone

speckit-clarify

Identify missing decisions in feature specifications and record clarification outcomes.

Community
Advanced
bryonjacobbryonjacob

software-architecture

Generate chat.md, tasks/, and metadata.json for GitHub issue planning.

Community
Basic
GratefulJinx77GratefulJinx77

speckit-plan

Generate a compliant implementation plan from a software spec template.

Community
Advanced
kimen-devkimen-dev

speckit-clarify

Scan feature specification documents for ambiguity and resolve gaps through interactive questioning.

Official
Advanced