ce-brainstorm
ce brainstorm
What it does
- output: alone (no value) → no-op, fall through to step 2.
- Read the document
- Confirm with the user before resuming: "Found an existing requirements-only plan for [topic]. Should I continue from this, or start fresh?"
- None of the software signals above are present
- The task describes something the user wants to explore, decide, or think through in a non-software domain
- Specific acceptance criteria provided
- Referenced existing patterns to follow
Requirements & configuration
- Neither (respond directly, skip all brainstorming phases) -- the input is a quick-help request, error message, factual question, or single-step task that doesn't need a brainstorm.
- The list is a view for the user, not an instruction to you. It does not change when a phase fires or what that phase requires, and it never substitutes for a phase's own exit condition.
- Make requirements concrete enough that planning will not need to invent behavior
Configuration: OUTPUT_FORMATSTRATEGYCONCEPTSSCRATCH_ROOTSCRATCH_DIR
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
ce-brainstorm FAQ
What does the ce-brainstorm skill do?
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know ("I know nothing about X but need to...") or asks for a blindspot pass — mapping the decision surface before questions begin. Not for executing already-specified work — direct implementation, debugging, or code review where no product scope is left to decide. Not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform — brainstorming scopes what to build, not whether to commit to an outside option. output: alone (no value) → no-op, fall through to step 2. Read the document
What does ce-brainstorm require?
Neither (respond directly, skip all brainstorming phases) -- the input is a quick-help request, error message, factual question, or single-step task that doesn't need a brainstorm. The list is a view for the user, not an instruction to you. It does not change when a phase fires or what that phase requires, and it never substitutes for a phase's own exit condition. Make requirements concrete enough that planning will not need to invent behavior Configuration keys: OUTPUT_FORMAT, STRATEGY, CONCEPTS, SCRATCH_ROOT, SCRATCH_DIR.
How do I install ce-brainstorm?
Run: npx -y skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-brainstorm --agent claude-code — the source lives at github.com/everyinc/compound-engineering-plugin.
Maintain ce-brainstorm?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[ce-brainstorm on getagentictools](https://getagentictools.com/skills/everyinc-compound-engineering-plugin-ce-brainstorm?ref=badge) npx agentictools info skills/everyinc-compound-engineering-plugin-ce-brainstorm The second line is the CLI lookup for this page — handy in READMEs and docs.
