搜索

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 仓库 Stars0 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

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

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-01-26
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

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