/analyze-and-plan
MUST USE when investigating a bug, CI failure, test failure, regression, incident, broken behavior, root cause, RCA, or debug-why problem before deciding whether to create an optim-plans solution plan; do not use for ordinary feature ideas, vague product planning, direct
$ npx -y skills add Optim-Agent/optim-plans --skill analyze-and-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/analyze-and-plan
Context preview
The summary Claude sees to decide when to auto-load this skill.
MUST USE when investigating a bug, CI failure, test failure, regression, incident, broken behavior, root cause, RCA, or debug-why problem before deciding whether to create an optim-plans solution plan; do not use for ordinary feature ideas, vague product planning, direct
Human-in-the-loop planning plugin for Claude and Codex: turn ideas into reviewed Markdown plans, record decisions, enforce explicit execution gates, and provide tested controller primitives for safer agent workflows.
Other skills on optim-plans.
- /big-plan
Use big-plan for broad or risky repo changes needing codebase inspection, websearch, and deeper refinement; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Open skill - /huge-plan
Use huge-plan for open-ended high-risk repo efforts needing websearch during brainstorming and refinement until convergence; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Open skill - /mini-plan
Use mini-plan for subtle low-risk repo changes needing one alignment question before execution; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Open skill - /optim-plans
MUST USE when a user asks to plan, brainstorm, design, scope, review, or evaluate a repo change before implementation; do not use for direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
Open skill - /plan
Use plan for normal repo changes needing bounded decisions, refinement, and high-priority review before execution; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Open skill - /research-and-plan
Alias for search-and-plan when external research should inform a repo-change plan before implementation.
Open skill