skills.rest
KamiJeong
KamiJeongCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Identify and resolve ambiguities in active feature specifications before implementation planning.

Updated May 18, 2026
Search Tags:#planning#requirements#acceptance criteria#ambiguity#product workflow#spec clarification
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-clarify-kamijeong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-clarify-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you remove ambiguity from an active feature spec so the team can plan and build with fewer misunderstandings, less rework, and clearer acceptance criteria.

Core Features & Use Cases

  • Targeted clarification: Identifies the most important missing decisions in a spec and turns them into concise questions.
  • Spec updates: Records the answers directly into the specification so the source of truth stays current.
  • Risk reduction: Focuses on the gaps that most affect implementation, testing, UX behavior, and operational readiness.
  • Use case: A product or engineering team uses it before planning a new feature to ensure scope, edge cases, and validation criteria are clear.

Quick Start

Ask the speckit-clarify skill to review the current feature spec and surface the highest-impact questions needed before planning.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I resolve ambiguities in a feature specification before planning?▼

To resolve ambiguities in a feature specification, identify missing decisions regarding scope, data rules, and UX flows, then turn them into concise questions. This process ensures clearer acceptance criteria and reduces implementation rework before planning begins.

How do I update acceptance criteria in a Spec Kit project structure?▼

You can update acceptance criteria in a Spec Kit project by recording clarified answers directly into the specification source. This requires a .specify directory and updates the active spec in place, keeping the source of truth current for implementation planning.

When do I need spec clarification for product workflow planning?▼

You need spec clarification for product workflow planning when an active feature spec has unclear scope, edge cases, or validation criteria. Clarifying these gaps beforehand focuses on the decisions that most affect implementation, testing, and operational readiness.

Does spec clarification work with a Spec Kit project directory?▼

Yes, spec clarification requires a Spec Kit project structure with a .specify directory to function. It applies to spec-driven feature work and updates the specification in place after each accepted clarification is provided.

What is the best way to find missing edge cases in a feature spec?▼

The best way to find missing edge cases is targeted clarification, which analyzes an active feature spec and surfaces the highest-impact questions. This risk reduction method focuses on gaps affecting implementation, testing, UX behavior, and operational readiness.

Related Skills

Explore More Product & Management Skills→
linhnguyen125linhnguyen125

speckit-clarify

Generate up to five targeted clarification questions for underspecified feature specs.

Community
Advanced
sambeausambeau
5

kanbanzai-specification

Draft testable specifications with acceptance criteria from approved designs.

Community
Intermediate
AcidicSoilAcidicSoil
1

refine-story

Refine rough user stories into sprint-ready documentation with acceptance criteria and technical guidance.

Community
Advanced
samcdavidsamcdavid
4

requirements-audit

Map acceptance criteria to code and document coverage gaps.

Community
Advanced