ce-brainstorm

Brainstorm collaborative dialogues to surface product requirements and decisions.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-brainstorm-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/ce-brainstorm
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-brainstorm-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative brainstorming helps teams clarify scope, surface options, and produce a durable requirements document before committing to implementation. It guides conversations when the user says "let's brainstorm" or when features are vague or ambitious, ensuring decisions are captured and planable.

Core Features & Use Cases

  • Guided, phase-based collaboration that surfaces decisions, constraints, and success criteria.
  • Produces a lightweight requirements document (or plan) that can be handed to planning, with optional visuals or diagrams.
  • Supports structured explorations when users request brainstorming, want problem framing, or need help deciding what to build.

Quick Start

Describe a feature idea to start the brainstorm and generate a durable requirements document.

Frequently Asked Questions about ce-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm product requirements when feature ideas are vague?

Structured brainstorming workflows guide teams through problem framing and decision capture to shape product requirements. By exploring options collaboratively, teams transform vague feature ideas into a durable requirements document ready for planning.

What is the best way to capture decisions during collaborative workshops?

Capturing decisions during collaborative workshops requires a phase-driven brainstorming process that systematically documents constraints and success criteria. This approach ensures cross-functional teams produce a planable requirements document for downstream implementation.

Can I generate a requirements document directly from early-stage idea exploration?

Generating a requirements document directly from early-stage idea exploration is possible through guided collaborative dialogues. The brainstorming workflow transforms ambitious feature concepts into a durable document with optional visuals for planning handoffs.

Does collaborative brainstorming work for cross-functional teams with ambitious scope?

Collaborative brainstorming supports cross-functional teams facing ambitious scope by providing a structured exploration process. It guides problem framing and option surfacing before implementation commitment, ensuring all team decisions are captured and planable.

How do I start a brainstorming session for product management planning?

Starting a brainstorming session for product management planning requires describing a feature idea to initiate the dialogue. The guided workflow then leads cross-functional teams through exploration phases, problem framing, and decision capture to produce a requirements document.

When should I use a structured brainstorming workflow instead of informal planning?

A structured brainstorming workflow is preferable to informal planning when features are vague or ambitious and require cross-functional alignment. It guarantees that decisions and constraints are captured in a durable requirements document for effective planning handoffs.