# Ce Brainstorm

Explore vague or ambitious ideas into a right-sized requirements-only unified plan.

- Repository: https://github.com/EveryInc/compound-engineering-plugin (25818 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add EveryInc/compound-engineering-plugin --skill ce-brainstorm -g -a claude-code -y`
Codex: `npx skills add EveryInc/compound-engineering-plugin --skill ce-brainstorm -g -a codex -y`
Cursor: `npx skills add EveryInc/compound-engineering-plugin --skill ce-brainstorm -g -a cursor -y`
Gemini CLI: `npx skills add EveryInc/compound-engineering-plugin --skill ce-brainstorm -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EveryInc/compound-engineering-plugin`

## Description

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Brainstorm a Feature or Improvement

Brainstorming answers **WHAT** to build through dialogue; `ce-plan` then enriches the same unified plan artifact with **HOW**. This skill does not implement code.

**Outcome:** a result sized to the work that `ce-plan` can build on without inventing product behavior, scope boundaries, or success criteria: a chat paragraph for Lightweight work, or a requirements-only unified plan under `<root>/plans/` when a file is earned.

**Done, on the brainstorm path:** that artifact is written and passes the Ready for Planning Check, or no file was written because the dialogue produced no decision that a later reader (the planner, a reviewer, or a future reader) needs recorded under a stable ID and the user asked for none, and Phase 4's handoff has been presented.

**Lightweight work ends in chat.** Phase 0.3 classifies the tier from the request and bounded inline reads before anything is dispatched; when the tier is uncertain, take the heavier one. Lightweight work, small, well-bounded, low ambiguity, ends in a chat paragraph with no file, no grounding scout, no approach generation, and no claim verifier. A file is earned only by a decision that a later reader needs recorded under a stable ID, or by the user asking for one.

**Stop and route instead** in three cases, decided by `references/phase-0.md`, not from memory. Each ends the run its own way, so the done condition above does not apply: non-software work, where `references/universal-brainstorming.md` replaces Phases 0.2, 4; a verdict question about a named external candidate, where you offer the `ce-pov` handoff; and neither, quick help, a factual question, a single-step task, answered directly.

The feature description is what the invocation carries, whether the user wrote it or a calling skill passed it. If none came, ask the user what they want to explore and do not proceed until you have one.

The rest: https://github.com/EveryInc/compound-engineering-plugin/blob/HEAD/skills/ce-brainstorm/SKILL.md