clarification-phase

Resolve spec.md ambiguities via structured questions and clarifications.md records.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill clarification-phase-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarification-phase
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/clarification-phase
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill clarification-phase-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined process to resolve ambiguities in spec.md by guiding users through a structured clarification phase using the AskUserQuestion tool, batching decisions (≤3 questions) and integrating answers back into the spec, with a formal clarifications.md record.

Core Features & Use Cases

  • Structured clarification workflow: Identify [NEEDS CLARIFICATION] markers, classify questions by priority (Critical/High), and limit to ≤3 questions.
  • AskUserQuestion orchestration: Batch questions, present concrete options, and collect answers synchronously.
  • Spec integration & traceability: Update spec.md with concrete requirements, remove markers, and generate clarifications.md as a historical record.
  • Commit and state tracking: Create commits and update state.yaml to reflect completion status.

Quick Start

Resolve ambiguities in spec.md using AskUserQuestion tool:

  1. Ensure spec.md exists and contains at least one [NEEDS CLARIFICATION] marker.
  2. Prepare a batched set of Critical/High questions (≤3) and call the AskUserQuestion tool.
  3. Integrate received answers into spec.md and generate clarifications.md; commit changes and update state.
  4. Review that no [NEEDS CLARIFICATION] markers remain and that a Clarifications (Resolved) section is added.

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?

To resolve ambiguities in a spec.md file, identify [NEEDS CLARIFICATION] markers, batch up to three Critical or High priority questions, and use the AskUserQuestion tool to collect synchronous answers for integration back into the spec.

What is the best way to batch clarification questions for project requirements?

The best way to batch clarification questions is to classify them by a prioritization matrix into Critical and High levels, limiting batches to a maximum of three questions to present concrete options synchronously to the user.

How do I track spec clarifications and maintain a historical record?

To track spec clarifications and maintain a historical record, generate a clarifications.md file after integrating answers, remove resolved markers from spec.md, commit changes to version history, and update tracking state in state.yaml.

Can I use AskUserQuestion to manage unresolved spec markers?

Yes, you can use AskUserQuestion to manage unresolved spec markers by orchestrating a structured clarification workflow that presents concrete options for each [NEEDS CLARIFICATION] tag and collects user decisions to update requirements.

Does the clarification workflow support automated spec updates?

Yes, the clarification workflow supports automated spec updates by integrating received answers directly into spec.md, removing the corresponding markers, and committing the finalized changes to version history.

When should I initiate a structured clarification phase for documentation?

You should initiate a structured clarification phase for documentation when your spec.md contains at least one [NEEDS CLARIFICATION] marker, ensuring unresolved ambiguities are formally addressed before proceeding.