Help us improve
Share bugs, ideas, or general feedback.
From cm
Brainstorms intent, requirements, and design before writing a structured plan. Use before any creative work or multi-step task to avoid premature coding.
npx claudepluginhub tody-agent/codymaster --plugin cmHow this skill is triggered — by the user, by Claude, or both
Slash command
/cm:cm-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Use before** any feature, behavior change, or 3+ step task
Guides structured brainstorming before any creative work: explores user intent, requirements, and design before implementation. Prevents wasted effort from unexamined assumptions.
Structured planning pipeline for medium/complex tasks: discover, classify, explore, detail, save, check, confirm, handoff. Invoked by the plan command to guide planning.
Strategic planning with auto-calibrated detail, decision rationale, and dependency ordering. Use when starting a new feature, bug fix, refactor, or any non-trivial work. Produces a plan document with tasks, reasoning, and acceptance criteria. Triggers: plan, planning, create plan, implementation plan, feature plan, work plan.
Share bugs, ideas, or general feedback.
openspec/changes/<name>/{design.md,tasks.md}.cm/handoff/plan.json (goal, decisions, first 3 tasks)cm-tdd or cm-executioncm-design-system.Red flags (STOP): code before brainstorm; assuming intent; skipping scope; "it's simple."
Write to openspec/changes/<initiative-name>/:
design.md
# Design: [Goal]
## Context & Technical Approach
## Proposed Changes
### [Component/File]
## Verification
tasks.md
# Implementation Checklist
- [ ] 1.1 ...
- [ ] 1.2 ...
- [ ] Verification testing
Plan rules: small testable steps (15-30 min each), order by dependency, verification per step. No vague steps.
Write .cm/handoff/plan.json:
{
"schema": "plan@1",
"goal": "...",
"decisions": ["..."],
"first_tasks": ["1.1", "1.2", "1.3"],
"openspec_path": "openspec/changes/<name>/"
}
Update .cm/CONTINUITY.md:
Token win: next session reads CONTINUITY (~200 tok) instead of full plan (2000+).
| After planning... | Use skill |
|---|---|
| Complex initiative | cm-brainstorm-idea (run BEFORE) |
| Need isolated workspace | cm-execution |
| Execute the plan | cm-execution |
| Tests first | cm-tdd |
| UI/frontend | cm-design-system |
Before writing the plan, surface what's uncertain instead of guessing:
Self-test: "Could a reviewer point to anything in this plan I'm guessing about?" If yes, mark it.
Think before you build. Document before you code. Emit handoff so the next skill picks up cold.