skills.rest
lofidonut3
lofidonut3COMMUNITY
Explore all skills by this author →
GitHub

speckit.clarify

Ask up to 5 targeted clarification questions and encode answers into a feature spec.

2|Updated Jan 21, 2026
Search Tags:#workflow#specification#questions#speckit#clarify#ambiguities
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-clarify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit.clarify
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/speckit.clarify
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. This helps ensure requirements are concrete and testable before any research or evaluation begins.

Core Features & Use Cases

  • Targeted clarification loop: asks up to 5 questions and logs answers back into the spec.
  • Seamless handoff: marks the spec as clarified and moves the workflow to the speckit.research phase.
  • Use case: when a feature is vague or multi-interpretive, run speckit.clarify after speckit.specify to lock down requirements.

Quick Start

Run the Speckit clarify command after speckit.specify to identify ambiguous areas. The tool loads the command file, processes syntax, conducts the one-by-one questioning loop, and updates the spec with responses. After completion, the spec status is set to clarified and you proceed to the /speckit.research phase.

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

To resolve ambiguities in a feature specification, run a targeted clarification workflow that asks up to 5 highly specific questions and encodes the answers back into the spec document to make requirements concrete and testable.

When should I clarify requirements before starting feature research?▼

You should clarify requirements before starting feature research when a feature is vague or multi-interpretive. Run this process immediately after initial specification to lock down requirements before moving to the research phase.

How do I make sure feature requirements are testable before development?▼

You make feature requirements testable by identifying underspecified areas in the spec and encoding concrete answers from a targeted questioning loop. This updates the spec to ensure all requirements are concrete before execution begins.

What is the best way to find underspecified areas in a spec document?▼

The best way to find underspecified areas in a spec document is to use an automated questioning workflow that analyzes the syntax and asks up to 5 highly targeted questions to pinpoint and resolve ambiguities.

Does the speckit.clarify workflow update the spec status automatically?▼

Yes, the speckit.clarify workflow updates the spec status automatically. After completing the questioning loop and encoding the answers, it marks the spec status as clarified and seamlessly transitions the workflow to the research phase.

Related Skills

Explore More Software Engineering Skills→
CongtrinhhCongtrinhh

speckit-clarify

Scan feature specs for ambiguity and collect up to five targeted answers.

Community
Advanced
lofidonut3lofidonut3
2

speckit.evaluate

Evaluate clarified Speckit specs against market research to refine features.

Community
Advanced
lofidonut3lofidonut3
2

speckit.specify

Convert natural-language feature descriptions into Speckit specifications.

Community
Advanced
nq-rdlnq-rdl

speckit-clarify

Generate targeted clarification questions and update feature specifications with answers.

Official
Advanced