AgentSkillsCN

aico-pm-clarification

通过结构化的提问来解决需求中的模糊之处：一次一个问题，同时提供推荐选项与相关理由。 独特价值：避免一次性向用户抛出过多问题，让用户感到不知所措。为每个决策提供专业的建议。 当满足以下条件时，可使用此技能： - 执行 /pm.clarify 命令； - 用户说“不清楚”、“不太明白这是什么意思”、“有点困惑”； - 用户询问“X 是什么意思？”、“X 应该如何运作？”、“你能帮我澄清一下吗？”； - 需求存在相互矛盾或不一致的细节； - 故事缺少验收标准，或存在内容空白； - 在开发正式展开之前，需要先填补信息缺口。 流程：每次只提一个问题（每轮最多 5 个问题），并附上推荐选项与相关理由。 切勿一次性提出多个问题——这会让用户感到不堪重负。

SKILL.md
--- frontmatter
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

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

markdown
### 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

CategoryFocus
ScopeWhat's included/excluded
BehaviorHow feature should work
DataWhat information is needed
Edge casesUnusual scenarios
Error handlingFailure 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