---

name: prd-clarify description: This skill should be used when the user asks to "clarify requirements", "refine the PRD", "ask clarifying questions", "fill in PRD gaps", "run a clarification session", or after generating a PRD that needs refinement. Uses structured questioning through AskUserQuestion tool to transform ambiguous requirements into actionable specifications.

PRD Clarification

Systematically analyze PRD documentation to identify ambiguities, gaps, and areas requiring clarification. Ask focused questions using the AskUserQuestion tool, adapting inquiry strategy based on each answer.

Initialization Protocol

Complete these steps in order:

Step 1: Locate PRD

Identify the directory containing the PRD file.

Step 2: Create Tracking Document

Create a tracking file in the same directory as the PRD:

• PRD feature-auth.md → create feature-auth-clarification-session.md

Initialize with:

Copy# PRD Clarification Session

**Source PRD**: [filename]
**Session Started**: [date/time]
**Depth Selected**: [pending]
**Progress**: 0/[pending]

---

## Session Log

Step 3: Select Depth

Use AskUserQuestion to determine scope:

Step 4: Update Tracking

Record selected depth and begin questioning.

Questioning Strategy

Prioritization Framework

1. Critical Path - Requirements blocking other features
2. High Ambiguity - Vague language, missing criteria
3. Integration Points - External systems, APIs
4. Edge Cases - Error handling, boundaries
5. Non-Functional - Performance, accessibility
6. User Journey Gaps - Missing steps, undefined states

Adaptive Questioning

After each answer:

• New ambiguity revealed? Prioritize it
• Related area clarified? Skip redundant questions
• Contradiction found? Address immediately
• New scope introduced? Flag for review

Question Quality Standards

Each question must be:

• Specific - Reference exact PRD sections
• Actionable - Answer informs requirement update
• Non-leading - Avoid suggesting the answer
• Singular - One clear question per turn
• Contextual - Acknowledge previous answers

Category Coverage

Distribute questions across:

1. User/Stakeholder clarity
2. Functional requirements
3. Non-functional requirements
4. Technical constraints
5. Edge cases & error handling
6. Data requirements
7. Business rules
8. Acceptance criteria
9. Scope boundaries
10. Dependencies & risks

Execution Rules

1. Create tracking doc first - Before ANY questions
2. Always use AskUserQuestion - Never ask in plain text; always provide 2-4 options
3. Complete full count - Ask all questions for selected depth
4. Track after every answer - Update document immediately
5. Adapt continuously - Reflect learnings in next question
6. Stay focused - Only PRD-related clarifications

Session Completion

After all questions:

1. Summarize key clarifications
2. List remaining ambiguities
3. Suggest priority for unresolved items
4. Offer to update PRD with clarified requirements

Tracking Format

Append after each question:

Copy## Question [N]
**Category**: [e.g., UX States, Error Handling]
**Ambiguity**: [What gap was identified]
**Question**: [What was asked]
**Response**: [User's answer]
**Clarified**: [How this resolves the ambiguity]

---

Additional Resources

Reference Files

For detailed question patterns and strategies:

• references/question-bank.md — 100+ categorized clarification questions
• references/sequencing-strategy.md — Phase-based questioning, adaptive flow
• references/scope-expansion.md — Handling discovered requirements

Example Files

Working examples in examples/:

• clarification-session.md — Complete 10-question session example

---

Quick Reference

Depth Selection

Scope Expansion Protocol

Decision Tracking Table

Maintain throughout session:

Copy## Decisions
| Question | Decision | Impact |
|----------|----------|--------|
| Auth scope? | OAuth + email | +1 day |
| i18n? | Deferred | None |

Effective Question Examples