Search

PythonReactSEOPDF
GitHub Skill

aico-pm-clarification

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.

yellinzero☆ 0 Repository stars0 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

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

Question Format

### Question [N]: [Topic]

**Context**: [Quote relevant requirement]

**Ambiguity**: [What's unclear]

**Options**:
| Option | Description | Implications |
|--------|-------------|--------------|
| A | [First option] | [Trade-offs] |
| B | [Second option] | [Trade-offs] |

**Recommended**: [Option] because [reasoning]

Ambiguity Categories

Category Focus
Scope What's included/excluded
Behavior How feature should work
Data What information is needed
Edge cases Unusual scenarios
Error handling Failure modes

Key Rules

  • ALWAYS ask ONE question per message, never batch
  • MUST provide recommended option with reasoning for each question
  • ALWAYS prioritize blocking issues (scope, security) over minor details
  • Max 5 questions per clarification session

Common Mistakes

  • ❌ Ask all questions at once → ✅ One at a time
  • ❌ Open-ended questions → ✅ Multiple choice with recommendation
  • ❌ Low-impact questions → ✅ Focus on blocking issues first

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-20
Index updated
2026-01-26
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!