afc:clarify

Resolve ambiguities in specification documents through targeted user questions.

7|Updated Feb 19, 2026

Search Tags:#documentation #specification #requirements #clarification #ambiguity #user feedback

Ready to run

npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-clarify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: afc:clarify
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/clarify
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses unclear or incomplete requirements in specifications by proactively asking clarifying questions to the user before proceeding with development tasks.

Core Features & Use Cases

Ambiguity Detection: Scans specifications for 10 common categories of ambiguity, including scope, data, UX flow, and non-functional requirements.
Targeted Questioning: Generates and presents prioritized questions to the user, one at a time, often with multiple-choice options.
Inline Spec Updates: Applies user-provided answers directly into the spec.md file, ensuring the specification remains current.
Use Case: When a feature requirement like "improve performance" is too vague, this skill will ask specific questions about target response times or resource utilization to define measurable goals.

Quick Start

Use the afc:clarify skill to resolve any ambiguities found in the current feature specification.

Frequently Asked Questions about afc:clarify

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

FAQPage Schema

How do I resolve ambiguities in a software specification document?▼

You resolve specification ambiguities by engaging in a targeted question-and-answer process that identifies incomplete requirements across ten categories, then applies your answers as inline updates directly to the spec file.

What categories of ambiguity should I look for in requirements clarification?▼

During requirements clarification, you should look for ambiguities across ten categories: necessity, scope, data, UX flow, non-functional qualities, external dependencies, edge cases, constraints, terminology, and completion criteria.

How do I clarify vague feature requirements before starting development planning?▼

You clarify vague feature requirements before development planning by generating prioritized, often multiple-choice questions one at a time to define measurable goals, such as specific target response times for performance improvements.

Can I update a specification file inline while answering clarification questions?▼

Yes, you can update a specification file inline while answering clarification questions, which ensures the document remains current and clear before you proceed to the development planning phase.

When should I not use an automated questioning process for spec ambiguity?▼

You should not use an automated questioning process for spec ambiguity if your requirements are already highly detailed, measurable, and lack incomplete data across the ten standard categorization checks.