AgentSkillsCN

aico-pm-brainstorming

引导用户通过结构化的对话，将模糊的想法转化为清晰、可操作的产品概念。采用一次一个问题的方式，并提供多项选择选项。 当满足以下条件时，可使用此技能： - 用户说“我有个想法”、“我想做点什么”、“让我好好想想”； - 用户提到“头脑风暴”、“探索想法”、“深入思考”； - 需求模糊、不完整，或用户似乎还不确定自己真正想要什么； - 在跳转到解决方案之前，需要先探索问题空间； - 执行 /pm.plan，但需求尚不清晰或缺乏上下文； - 用户问“我该做什么？”、“这个东西该怎么运作？”。 流程：每次只提一个问题，优先选择多项选择，在最终定下方案前，先探索 2–3 种可能的思路。

SKILL.md
--- frontmatter
name: aico-pm-brainstorming
description: |
  Guide users through structured dialogue to transform vague ideas into clear, actionable product concepts. Uses one-question-at-a-time approach with multiple choice options.

  Use this skill when:
  - User says "I have an idea", "I want to build", "let me think about"
  - User mentions "brainstorm", "explore ideas", "think through"
  - Requirements are vague, incomplete, or user seems unsure what they want
  - Need to explore problem space before jumping to solutions
  - Running /pm.plan but requirements are unclear or missing context
  - User asks "what should I build?", "how should this work?"

  Process: Ask ONE question at a time, prefer multiple choice, explore 2-3 approaches before settling.

Brainstorming

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. •Check context: Scan docs/reference/pm/ for existing product context
  2. •Understand problem: Ask clarifying questions one at a time
  3. •Explore alternatives: Propose 2-3 approaches with trade-offs
  4. •Validate concept: Present ideas in small sections (200-300 words), confirm each
  5. •Document outcome: Save validated concept for next steps

Core Pattern

PhaseActionOutput
UnderstandAsk clarifying questions one at a timeProblem statement
ExplorePropose 2-3 approaches with trade-offsSelected approach
ValidatePresent concept in small sectionsValidated concept

Key Rules

  • •ALWAYS ask ONE question per message - never overwhelm with multiple questions
  • •MUST prefer multiple choice over open-ended questions when possible
  • •ALWAYS explore 2-3 alternative approaches before settling on one
  • •Present ideas incrementally in 200-300 word sections, confirm each before continuing

Question Examples

  • •"What problem are you trying to solve for users?"
  • •"Who is the primary user for this feature?"
  • •"What does success look like? (A) metric improvement (B) user satisfaction (C) both"

Common Mistakes

  • •❌ Ask multiple questions at once → ✅ One question per message
  • •❌ Jump to solutions immediately → ✅ Understand problem first
  • •❌ Skip alternatives → ✅ Always explore 2-3 approaches

Iron Law

NO IMPLEMENTATION DISCUSSION DURING BRAINSTORMING

This rule is non-negotiable. During brainstorming:

  1. •Focus only on WHAT, never HOW
  2. •No code, no architecture, no technical details
  3. •Capture all ideas without judgment
  4. •Defer feasibility analysis to later phases

Rationalization Defense

ExcuseReality
"I already know what to build"Unvalidated assumptions cause 3x rework
"Let's save time and discuss implementation"Premature optimization kills innovation
"The solution is obvious"Obvious solutions often miss edge cases
"We don't have time for this"1 hour of brainstorming saves 3 days of rework