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 implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
npx skills add Optim-Agent/optim-plans --skill analyze-and-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyze and Plan Use this skill for problem/failure inputs that need diagnosis before planning. Do not use it for ordinary feature planning, direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests. ## Workflow 1. Inspect available evidence first: repo files, logs, tests, command output, or user-provided symptoms. 2. Produce an in-message RCA summary before asking whether to plan. Use at most 5 Whys. Stop with `unknown` when evidence is insufficient; do not invent a cause. 3. Ask one choice prompt that includes the RCA summary. The choices are: recommended first to call `optim-plans`, second to review the summary only without a plan, `Other` second-last, and `Auto-complete` last. 4. On opt-out, stop after the summary. Do not write `PROBLEM_ANALYSIS.md` on opt-out. 5. On opt-in or Auto-complete choosing the recommendation, select the smallest fitting planning level, read and follow `../{selected-level}/SKILL.md`, and preserve that skill's first-turn contract. 6. Pass the original problem, RCA summary, evidence, and `PROBLEM_ANALYSIS.md` artifact intent as the planning request. The selected planning skill must initialize c
- Workflow
- Level Selection
- PROBLEMANALYSIS.md
What does the analyze-and-plan skill do?
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 implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
How do I install it?
Run `npx skills add Optim-Agent/optim-plans --skill analyze-and-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Optim-Agent/optim-plans, a repository with 288 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.