Ce Ideate

This runs ahead of brainstorming to answer "what's worth exploring?" rather than "how should we build it?" It grounds in your actual codebase first, generates a batch of ideas, then explicitly critiques and rejects most of them with reasons instead of just ranking everything optimistically. The output is a ranked artifact in docs/ideation/ that routes into ce-brainstorm for the detailed work. It can resume recent ideation sessions if you left something open, and it has a surprisingly careful scope gate that asks whether you actually named a subject before spinning up the machinery. The questioning discipline is strict: it only asks what's needed to identify a topic, never solution constraints or audience, because those belong in brainstorming. Honest take: the rejection mechanism is the real quality lever here, not the generation volume.

skills.sh installs: 3.5K
GitHub stars: 26K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add everyinc/compound-engineering-plugin --skill ce-ideate --agent claude-code

Installs into .claude/skills of the current project.

Files

Generate Improvement Ideas

ce-ideate runs before ce-brainstorm. This skill answers "which ideas are worth exploring?" ce-brainstorm then answers what one chosen idea should mean. ce-plan answers how it gets built.

Done: a ranked ideation artifact is written to <root>/ideation/ when that root is present, else to a CE temp path. Every idea generated has been critiqued, and the survivors are explained. The user is left holding the next-steps menu. No requirements, plans, or code.