aico-pm-clarification

name

aico-pm-clarification

description

Resolve requirement ambiguities through STRUCTURED questioning: one question at a time, with recommended options and reasoning. UNIQUE VALUE: Prevents overwhelming users with multiple questions. Provides expert recommendations for each decision. Use this skill when: - Running /pm.clarify command - User says "unclear", "not sure what this means", "confused about" - User asks "what does X mean?", "how should X work?", "can you clarify?" - Requirements have conflicting or inconsistent details - Stories are missing acceptance criteria or have gaps - Need to fill information gaps BEFORE development can proceed Process: Ask ONE question at a time (max 5 per session), provide recommended option with reasoning. DO NOT ask multiple questions at once - this overwhelms users.

Requirement Clarification

⚠️ CRITICAL RULES - READ FIRST

1. SEARCH FIRST: Always search docs/reference/pm/ for related documents before asking questions
2. ONE QUESTION AT A TIME: Max 5 questions per session
3. UPDATE DOCUMENTS: After clarification, update the relevant story/version files

Language Configuration

Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.

Process

1. Scan context: Check docs/reference/pm/ for existing documentation
2. Identify ambiguities: Categorize by type (scope, behavior, data, edge cases)
3. Prioritize: Sort by impact: scope > security > UX > technical
4. Ask ONE question at a time: Max 5 questions per session
5. Provide recommendation: Each question should have a recommended option with reasoning
6. Update docs: Document each answer immediately