speckit-clarify

Identify missing decisions in feature specifications and record clarification outcomes.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ztwosone/GreedySnake --skill speckit-clarify-ztwosone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/ztwosone/GreedySnake/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/ztwosone/GreedySnake --skill speckit-clarify-ztwosone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces ambiguity in feature specifications by identifying missing decisions, asking targeted clarification questions, and incorporating validated answers into the spec.

Core Features & Use Cases

  • Specification Analysis: Reviews active feature specs for gaps across requirements, data models, UX flows, quality attributes, integrations, and acceptance criteria.
  • Clarification Workflow: Generates prioritized questions, evaluates recommended answers, and records accepted decisions directly into specification documents.
  • Use Case: Help a development team prepare a detailed feature specification before implementation by resolving unclear requirements and improving downstream planning accuracy.

Quick Start

Use the speckit-clarify skill to analyze the current feature specification and ask the most important clarification questions.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I resolve ambiguity in feature specifications before development?

Resolving ambiguity in feature specifications involves analyzing active spec files to identify missing decisions, generating prioritized clarification questions, and writing validated answers directly into the specification documents.

What is specification clarification in software development?

Specification clarification is the process of reviewing feature requirements, data models, and acceptance criteria to find gaps, ask targeted questions, and record accepted decisions to improve downstream planning accuracy.

How do I prepare a detailed feature specification for implementation?

Preparing a detailed feature specification requires reviewing requirements and UX flows for gaps, evaluating recommended answers to targeted clarification questions, and recording accepted decisions directly into the specification documents.

Do I need a spec-kit directory structure to use feature planning clarification?

Yes, feature planning clarification requires a spec-kit directory structure containing validation scripts and specification files to perform interactive clarification updates successfully.

What are the limitations of automated specification clarification?

Automated specification clarification is limited to identifying missing decisions within existing requirements, data models, and acceptance criteria, meaning it cannot generate entirely new feature concepts or replace human architectural decisions.