smithery/yellinzero

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 - St…

Installation

$ npx skills add smithery/yellinzero --skill aico-pm-clarification

Also in this package

Other skills from smithery/yellinzero.

npx skills add smithery/yellinzero

Browse all from smithery/yellinzero

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,979 B
  • docs SUMMARY.md 820 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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