ce-brainstorm

Guide structured brainstorming to surface requirements and document decisions.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-brainstorm-datorresb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-brainstorm
Source: https://github.com/datorresb/discovery-event-platform/tree/main/.github/skills/ce-brainstorm
Command: npx skills add https://github.com/datorresb/discovery-event-platform --skill ce-brainstorm-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative teams often struggle to translate vague ideas into concrete planning steps; this skill provides a structured, repeatable brainstorm workflow to surface requirements and approach before planning implementation.

Core Features & Use Cases

  • Guided, multi-phase brainstorming process that surfaces requirements, constraints, and success criteria.
  • Lightweight repository research and questions-driven dialogue to align stakeholders.
  • Documented decisions and open questions ready for /ce-plan handoff.

Quick Start

Start a brainstorm by describing the feature or problem you want to explore, then follow the guided prompts to surface requirements and next steps.

Frequently Asked Questions about ce-brainstorm

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

FAQPage Schema
How do I brainstorm feature requirements collaboratively before planning implementation?▼

Feature requirements brainstorming is guided through a structured, multi-phase dialogue that surfaces constraints, success criteria, and open questions before planning implementation.

What is the best way to capture decisions and open questions during an ideation session?▼

Capturing decisions and open questions during ideation is handled by enforcing a disciplined process that documents artifacts and aligns stakeholders for future reference.

How do I align stakeholder goals when translating vague ideas into planning steps?▼

Aligning stakeholder goals requires a questions-driven dialogue and lightweight repository research to translate vague ideas into structured planning steps collaboratively.

Can I use a structured brainstorming workflow to assess constraints for product management?▼

A structured brainstorming workflow assesses constraints and requirements for product management by guiding users through enforced phases, questions, and documentation artifacts.

Do I need prior documentation to start a brainstorming session for feature ideation?▼

Prior documentation is not required to start brainstorming feature ideation; simply describe the feature or problem, then follow guided prompts to surface requirements.

When should I avoid using a guided brainstorming workflow for requirements gathering?▼

Guided brainstorming workflows should be avoided when rapid, informal ideation is needed without structured decision capture, stakeholder alignment, or documented planning artifacts.