skills.rest
Arthur-Valentim
Arthur-ValentimCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Detect and resolve ambiguities in software feature specifications by asking targeted questions.

Updated May 9, 2026
Search Tags:#software development#specification#clarification#feature spec#spec-Kit
One-click install
npx skills add https://github.com/Arthur-Valentim/TODO---LIST --skill speckit-clarify-arthur-valentim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Arthur-Valentim/TODO---LIST/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Arthur-Valentim/TODO---LIST --skill speckit-clarify-arthur-valentim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill addresses the challenge of identifying and resolving ambiguities in feature specifications, providing targeted clarification to ensure a well-defined and actionable spec.

Core Features & Use Cases

  • Clarity Identification: Identifies underspecified areas in a feature spec by posing up to 5 targeted questions.
  • Integration: Integrates clarifications back into the spec, reducing rework risk and improving spec quality.
  • Use Case: Utilize this Skill when preparing for development to ensure your spec is comprehensive and actionable, potentially saving time and effort in the long run.

Quick Start

Run the clarify command on your spec to start the clarification process.

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 software feature specification?▼

To resolve ambiguities in a feature specification, you can run a clarification process that poses up to 5 targeted questions to identify underspecified areas and encodes the answers directly back into the spec.

What is the best way to find underspecified areas in a feature spec before development?▼

Finding underspecified areas in a feature spec requires targeted questioning to detect ambiguities. This ensures the specification is comprehensive and actionable, reducing rework risk before development begins.

How do I integrate clarifications back into a feature specification?▼

You integrate clarifications back into a feature specification by answering targeted questions during the clarification process. The system automatically encodes these answers directly into your existing spec file.

Do I need a specific project structure to clarify feature specs?▼

Yes, you need a Spec-Kit project structure to clarify feature specs. The process requires a .specify/ directory presence within your project to operate correctly.

Why does my feature spec need targeted clarification before coding?▼

Your feature spec needs targeted clarification to ensure it is well-defined and actionable. Identifying ambiguities early through targeted questioning saves time and effort by preventing rework during development.

How many questions are asked when clarifying a software feature spec?▼

When clarifying a software feature spec, the process poses a maximum of 5 targeted questions to identify and resolve ambiguities, ensuring the specification is comprehensive without overwhelming the user.

Related Skills

Explore More Software Engineering Skills→
WayneSHCWayneSHC
1

speckit-clarify

Identify underspecified areas in feature specifications and encode answers back into the spec.

Community
Intermediate
skinred78skinred78
1

research

Analyze technical requirements and produce citation-rich research reports with implementation guidance.

Community
Advanced
WayneSHCWayneSHC
1

speckit-checklist

Generate custom checklists to validate feature requirements in spec-kit projects.

Community
Advanced
reason-healthcarereason-healthcare
12

speckit-clarify

Identify underspecified areas in feature specifications and log clarifications.

Official
Advanced