What problem does it solve?
Teams often waste time and resources implementing features that don't align with user needs or business goals because vague, ambiguous feature ideas are not clarified before planning and coding begins. This Skill eliminates that risk by guiding collaborative dialogue to surface product decisions, scope boundaries, and success criteria before any implementation work starts.
Core Features & Use Cases
- Collaborative Requirement Exploration: Guides step-by-step, one-question-at-a-time dialogue to clarify vague feature ideas, challenge assumptions, and explore multiple solution options without jumping to implementation details.
- Right-Sized Requirements Documentation: Produces a durable, lightweight requirements document that captures all product decisions needed for planning, eliminating the need for downstream teams to invent scope, behavior, or success criteria.
- Flexible Scope Handling: Adapts its workflow to lightweight, standard, or deep work scopes, skipping unnecessary steps for small, well-defined tasks while providing thorough guidance for complex, cross-cutting initiatives.
- Use Case Example: Use this Skill when a stakeholder says "let's brainstorm a new user onboarding flow", when you have a vague feature request with multiple possible implementations, or when you need to align on success criteria before writing a technical plan.
Quick Start
Use the ce:brainstorm skill to explore your vague feature idea or problem through guided collaborative questions to produce a clear, actionable requirements document for implementation planning.
