Ce Plan

Turns "build a dashboard" or "add OAuth" into structured implementation plans without writing the code for you. It researches your codebase first, maps decisions to specific files (with repo-relative paths), and lists concrete test scenarios so you're not guessing at coverage later. Works standalone or deepens existing plans through an interactive review flow. The output stays portable as markdown or HTML, good for PRs or issue bodies, not just internal tooling. Pairs with ce-brainstorm for requirements and ce-work for execution. Honest take: the planning bootstrap and clarifying question flow means it won't bail when your input is vague, which cuts down on the "I just wanted help" frustration.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Create Technical Plan

Outcome: a plan for carrying out and checking the agreed work while preserving its outcome and constraints. Resolve technical choices from evidence; leave adequate instructions unchanged. ce-brainstorm defines WHAT, ce-plan plans HOW, and ce-work executes. A prior brainstorm is optional.

An explicit invocation always produces a plan. Never classify a direct invocation as "not a planning task" and route out. It may select any output contract below, and the smallest valid plan is a few sentences in chat.

Research, decide, and write the plan — never implement. Do not write production code, run tests, or learn from execution-time results. Directional pseudo-code and grammar sketches may communicate design; changing code to see what happens belongs in ce-work.