clarification-phase

Name: clarification-phase
Availability: InStock
Author: DYAI

Resolve [NEEDS CLARIFICATION] markers in spec.md by batching questions and updating documentation.

Updated Feb 14, 2026

Search Tags:#workflow #planning #documentation #requirements #clarification #spec #AskUserQuestion

Ready to run

npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill clarification-phase-dyai2025

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarification-phase
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/clarification-phase
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill clarification-phase-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams resolve ambiguities in specifications by guiding structured clarification processes using AskUserQuestion, batching questions, and recording outcomes.

Core Features & Use Cases

Structured clarification orchestration: identifies [NEEDS CLARIFICATION] markers, prioritizes questions into Critical/High, and batches up to three inquiries per AskUserQuestion call.
Documentation generation: updates the spec.md with concrete requirements once answers are provided and creates a clarifications.md historical record.
Traceability and state management: updates state.yaml to reflect completion and maintains a centralized trace of decisions for planning and audits.

Quick Start

Run the clarification workflow on spec.md to resolve markers and finalize planning-ready requirements.

Frequently Asked Questions about clarification-phase

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

FAQPage Schema

How do I resolve ambiguities in a spec.md file with NEEDS CLARIFICATION markers?▼

This Skill automates structured clarification workflows to resolve spec.md ambiguities by identifying NEEDS CLARIFICATION markers, batching up to three questions per AskUserQuestion call, and updating the spec with concrete requirements once answers are provided.

How does the AskUserQuestion batching process work for requirements clarification?▼

The clarification process batches questions into Critical and High priority categories, asking up to three inquiries per AskUserQuestion call to efficiently resolve ambiguities and finalize planning-ready requirements without overwhelming the user.

What is the best way to maintain traceability for resolved specification ambiguities?▼

Maintaining traceability involves generating a clarifications.md historical record and updating state.yaml to reflect completion, ensuring a centralized trace of decisions for planning and audits after resolving spec ambiguities.

Can I use this structured clarification workflow for planning and audit preparation?▼

Yes, this structured clarification workflow supports planning and audits by updating state.yaml to reflect completion and maintaining a centralized trace of decisions alongside a clarifications.md historical record of resolved requirements.

What limitations exist when using AskUserQuestion for spec clarification?▼

A key limitation is that the AskUserQuestion mechanism batches a maximum of three inquiries per call, meaning highly ambiguity-heavy requirements will require multiple sequential interactions to fully resolve all NEEDS CLARIFICATION markers.