clarify

Convert ambiguous user requests into detailed, testable specifications.

5|Updated Mar 16, 2026

Search Tags:#code review #specification #requirement clarification #structured dialogue #testable spec

Ready to run

npx skills add https://github.com/yash-gadodia/claude-init --skill clarify-yash-gadodia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/yash-gadodia/claude-init/tree/main/templates/skills/clarify
Command: npx skills add https://github.com/yash-gadodia/claude-init --skill clarify-yash-gadodia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in converting ambiguous or multi-interpretable requests into clear, testable specifications, ensuring that the intent and requirements are well-defined before implementation.

Core Features & Use Cases

Structured Dialogue: Guides through a process of exploring context, clarifying intent, proposing approaches, and writing specifications.
Automated Review: Offers an automated spec reviewer to ensure completeness, testability, and adherence to scope.
User Approval: Ensures that the spec is reviewed and approved by the user before proceeding to implementation.

Quick Start

Use the /clarify command to start the process of turning a vague request into a structured spec.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I turn a vague software request into a testable specification?▼

Requirement clarification transforms ambiguous requests into testable specifications by guiding you through a structured dialogue to explore context, clarify intent, propose approaches, and write a detailed spec for user approval.

What is requirement clarification and when do I need it for code review?▼

Requirement clarification is the process of converting ambiguous requests into clear, testable specifications. You need it before code review or implementation to ensure intent and requirements are well-defined and multi-interpretable requests are resolved.

How do I write a testable spec from an ambiguous feature request?▼

Writing a testable spec involves exploring the context of the feature request, clarifying the underlying intent, proposing technical approaches, and drafting the specification. An automated review step then ensures the spec is complete and testable before user approval.

Can I automate the review of a written specification for completeness and scope?▼

Yes, you can automate specification review to verify completeness, testability, and scope adherence. An automated spec reviewer evaluates the drafted requirements against these criteria before presenting the final spec for user approval.

What is the best way to structure a dialogue for requirement clarification?▼

The best way to structure a requirement clarification dialogue is to sequentially explore the context, clarify the user's intent, propose technical approaches, and write the specification. This structured process ensures ambiguous requests become testable specs.

Why does my software specification fail to capture the actual project intent?▼

Your specification fails to capture project intent when requirement clarification is skipped, leaving ambiguous requests unresolved. Using a structured dialogue to explore context and clarify intent before writing the spec ensures the actual requirements are well-defined.