skills.rest
xyphyx
xyphyxOFFICIAL
Explore all skills by this author →
GitHub

speckit-clarify

Identify underspecified areas in feature specifications and generate prioritized clarification questions.

Updated Apr 8, 2026
Search Tags:#specification#requirements#product-management#stakeholders#feature-spec#clarify
One-click install
npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-clarify-xyphyx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/xyphyx/internal-project-template/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-clarify-xyphyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature specification and generate concise, answerable clarifications.

Core Features & Use Cases

  • Structured ambiguity detection across functional requirements, data models, UX interactions, non-functional criteria, and edge cases.
  • Interactive, one-question-at-a-time clarification loop that yields up to five high-impact questions.
  • Automatic embedding of accepted answers into a dedicated Clarifications section in the spec, with traceable updates after each acceptance.

Quick Start

Describe or supply a current feature spec to initiate the clarifications flow.

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

Feature specification ambiguity is identified by analyzing functional requirements, data models, UX interactions, non-functional criteria, and edge cases to generate concise, answerable clarifications for stakeholders.

What is the best way to clarify requirements with stakeholders for product management?▼

The best way to clarify requirements is using an interactive, one-question-at-a-time loop that surfaces up to five high-impact questions, ensuring stakeholders address critical specification gaps without being overwhelmed.

How do I track clarifications and accepted answers within a feature spec?▼

Accepted answers are automatically applied to the feature spec in a dedicated, traceable Clarifications section after each acceptance, maintaining a clear record of updated functional requirements and edge case decisions.

Can I use targeted questions to detect missing edge cases in my product spec?▼

Yes, targeted questions are generated specifically to detect missing edge cases, alongside gaps in non-functional criteria and UX interactions, prioritizing the most high-impact underspecified areas for stakeholders to resolve.

Do I need to supply a complete feature spec to start generating clarifications?▼

You do not need a complete feature spec; you simply describe or supply a current draft of the feature specification to initiate the interactive clarifications flow and begin surfacing targeted questions.

Related Skills

Explore More Product & Management Skills→
reckerswartzreckerswartz

refine-spec

Refine draft feature specifications into structured implementation-ready documents.

Community
Intermediate
erikaliraerikalira
1

speckit-clarify

Identify underspecified areas in feature specs by asking up to five clarification questions.

Community
Advanced
CoWork-OSCoWork-OS
420

prd

Generates structured Product Requirements Documents with goals, user stories, and acceptance criteria.

Official
Advanced
wahidyankfwahidyankf
9

gherkin-acceptance-criteria

Write Gherkin acceptance criteria using Given-When-Then syntax.

Community
Advanced