clarification-phase

Generate structured clarification questions for specification documents with ambiguity markers.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/oxie/portfolio-cms-project --skill clarification-phase-oxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarification-phase
Source: https://github.com/oxie/portfolio-cms-project/tree/main/.claude/skills/clarification-phase
Command: npx skills add https://github.com/oxie/portfolio-cms-project --skill clarification-phase-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically resolves ambiguities in feature specifications by generating structured questions, prioritizing them, and integrating answers back into the specification. It prevents misinterpretations, reduces rework, and ensures clear, actionable requirements before planning begins.

Core Features & Use Cases

  • Question Generation: Extracts ambiguities from spec.md and formats them into precise, structured questions for stakeholders.
  • Prioritization Matrix: Helps identify and focus on critical (scope, security, breaking changes) and high-priority (UX) questions, limiting the number of questions asked.
  • Assumption Documentation: Documents medium/low priority questions as informed guesses with rationale, avoiding unnecessary back-and-forth.
  • Spec Integration: Integrates user answers directly into spec.md, removing ambiguity markers and updating requirements.
  • Use Case: A feature specification has several unclear points. This skill helps formulate precise questions for stakeholders, get clear answers, and update the spec, ensuring everyone is aligned before development starts.

Quick Start

Clarify the 'Student Progress Dashboard' feature, generating structured questions for any ambiguities in the spec.

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 feature specifications before development starts?

Resolve ambiguities by extracting unclear points from specification documents, generating structured clarification questions, prioritizing them by impact (scope, security, UX), and integrating stakeholder answers back into the spec to ensure alignment.

What's the best way to prioritize clarification questions across multiple specs?

Prioritize clarification questions using a matrix that flags critical issues (scope changes, security, breaking changes) first, then high-priority concerns (UX), and documents medium/low-priority assumptions with rationale to avoid unnecessary back-and-forth.

How do I document and track answers to specification clarifications?

Document clarification answers in a structured format (clarifications.md), update the original specification with resolved ambiguities, and maintain workflow state to track which specs have been clarified and which remain pending.

Can I use clarification questions to prevent rework and misinterpretation in product planning?

Yes. Systematic clarification before planning prevents costly misinterpretations by extracting ambiguities upfront, getting explicit stakeholder answers, and integrating them into requirements so teams move forward with shared understanding.

What should I do with low-priority ambiguities that don't need stakeholder input?

Document low-priority ambiguities as informed assumptions with clear rationale in your clarifications file, bypassing unnecessary stakeholder questions while maintaining transparency about decisions made during the clarification phase.