ce-brainstorm
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.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-brainstorm ~/.claude/skills/ce-brainstormFrom README
Brainstorm a Feature or Improvement Note: The current year is 2026. Use this when dating requirements-only unified plans. Brainstorming helps answer WHAT to build through collaborative dialogue. It precedes ce-plan, which enriches the same unified plan artifact with HOW to build it. The durable output of this workflow is a requirements-only unified plan. In other workflows this might be called a lightweight PRD or feature brief. In compound engineering, keep the workflow name brainstorm, but write the first version of the plan artifact under /plans/ with artifactreadiness: requirements-only so planning does not need to invent product behavior, scope boundaries, or success criteria. This skill does not implement code. It explores, clarifies, and documents decisions for later planning or execution. Core Principles Assess scope first - Match the amount of ceremony to the size and ambiguity of the work.