brainstorm-ideas
Facilitate divergent idea generation before product planning, then converge only when the user is ready. Use when the user asks to brainstorm, ideate, generate options, or get beyond the obvious approaches.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- brainstorm-ideas
- license
- MIT
- description
- Facilitate divergent idea generation before product planning, then converge only when the user is ready. Use when the user asks to brainstorm, ideate, generate options, or get beyond the obvious approaches.
03 SKILL.md 正文
Brainstorm Ideas
Generate a broad option space before evaluating it. Read
../../references/planning-artifacts.md for persistence
and handoff rules.
Set the stance
Confirm the topic, the goal behind the session, and one stance:
- Facilitator: supply prompts and techniques, never ideas.
- Creative partner: facilitate and contribute ideas, clearly attributing them.
- Ideate for me: run the divergent pass autonomously and present the result.
Hold the stance for the run. In dialogue, ask one generative prompt at a time.
Diverge
Do not organize or conclude too early. Change creative domain or technique every 5–10 turns, using constraints, analogies, inversions, stakeholder viewpoints, combinations, and failure-first prompts. Aim well beyond the first obvious batch; breadth matters more than polished wording.
Append every idea and meaningful direction to idea/.decision-log.md when persisting. Do not turn
raw ideas into requirements during divergence.
Converge
Converge only when the user asks or the topic is exhausted. Cluster by underlying opportunity, name surprising combinations, and evaluate against criteria derived from the session goal. Preserve minority ideas with high upside instead of averaging everything into safe consensus.
Produce idea/BRAINSTORM-INTENT.md containing only the selected directions, rejected directions
whose reason matters, decision criteria, and unresolved questions. Offer forge-idea for pressure
testing or product-spec when the chosen intent is already defined.
Adapted from BMad Method's brainstorming workflow (MIT, BMad Code, LLC).
04 同仓库更多 Skills
validate-artifact
Validate a single agile artifact (Epic, Feature, User Story, or Task) against the toolkit rule set. Use when the user asks to "validate this story/feature/epic", "check this ticket", "is this artifact ready?", or provides a local draft path or provider item and wants a quality report. Accepts a local draft or a tracker work item. Runs all checks non-blocking and emits a terminal report + persisted report. One artifact per invocation.
split-story
Lateral story-sizing skill. Takes a single User Story and determines if it should be split, how many sub-stories to create, and what split pattern to use — then drafts sub-stories and hands them off. Use when the user asks "split this story", "is this story too big?", "analyze this story for sizing", or provides an artifacts path / tracker id / file path / raw text and wants a split recommendation. One story per invocation.
research-decision
Research a product, market, domain, competitor, user, or technical question in service of a named decision, producing a cited decision brief. Use when planning depends on current evidence rather than more ideation.
product-spec
Distill an idea, brief, PRD, UX contract, architecture spine, issue, or mixed notes into a compact canonical product contract with stable capabilities and companions. Use before backlog decomposition when intent is defined; update or validate an existing product spec through the same skill.
product-requirements
Create, update, or validate a right-sized Product Requirements Document with stable requirements, explicit scope, user journeys where useful, and measurable outcomes. Use for multi-person or multi-epic alignment; skip it when a concise product spec is enough.
product-brief
Create, update, or validate a concise product brief that captures a clear concept, its users, value, scope, and success criteria. Use when the user wants a one- or two-page product narrative before a PRD or product spec.