ce-brainstorm_skill

Overview

This skill guides collaborative brainstorming to clarify what to build and produces a right-sized requirements document suitable for planning. It helps surface options, resolve product decisions, and leave implementation details for a follow-up planning step. Use it when scope is unclear, the user asks to brainstorm, or when a vague or ambitious feature needs framing.

How this skill works

The workflow resumes existing brainstorms when present, assesses whether brainstorming is needed, and classifies scope as lightweight, standard, or deep. It runs a short context scan, performs product pressure-testing, conducts focused one-question-at-a-time dialogue, proposes 2–3 concrete approaches when useful, and captures durable decisions in a compact requirements document dated in 2026. Implementation details are intentionally excluded unless the brainstorm is technical.

When to use it

• User says “let’s brainstorm” or asks “what should we build?”
• Feature request is vague, ambitious, or has multiple valid solutions
• You need to decide product-facing behavior, scope, or success criteria
• There’s an existing partial requirements doc that needs resuming
• Before /ce:plan to avoid leaving product decisions for planners

Best practices

• Ask one question at a time and prefer single-select choices for direction
• Right-size the artifact: compact brief for small work, fuller doc for larger work
• Resolve product decisions here; keep implementation details for planning
• Surface dependencies and blocking questions explicitly as Resolve Before Planning
• Apply YAGNI to carrying cost — prefer simplest meaningful solutions

Example use cases

• Clarify scope and success criteria for a requested new feature with fuzzy goals
• Explore alternatives and recommend a direction for a cross-team product change
• Resume and finalize an existing brainstorm found in docs/brainstorms/
• Turn a stakeholder’s ‘help me think through X’ into a short requirements doc
• Compare low-effort polish vs. larger overhaul and recommend the high-leverage move