Diagnose before plan

Skill Optim-Agent/optim-plans/skills/diagnose-before-plan

Diagnose failures before creating a Prime Agent plan. MUST USE for bugs, CI failures, test failures, regressions, incidents, broken behavior, root cause, RCA, or debug-why requests before deciding whether to plan; preserve language, reviewer, and criticizer settings in .git/optim-plans; exclude ordinary feature planning, direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.From its SKILL.md

Install

npx -y skills add Optim-Agent/optim-plans --skill diagnose-before-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Diagnose Before Plan

Use this skill for problem or failure inputs that need diagnosis before planning.

Setup

Read ../_shared/references/prime-planning-workflow.md, ../_shared/references/state-and-config.md, and ../_shared/references/plan-artifact-template.md.
Use .git/optim-plans for controller state and docs/optim-plans/YYYY-MM-DD-topic/ for public artifacts.
Preserve reviewer and criticizer settings for any selected planning skill.

Diagnostic Workflow

Inspect available evidence first: repository files, logs, tests, command output, stack traces, recent diffs, CI output, environment details, and user-provided symptoms.
Produce an in-message RCA summary before asking whether to plan. Use at most 5 Whys. Stop with unknown when evidence is insufficient.
Ask one choice prompt in the configured language:
1. Create the scoped fix plan - recommended when evidence supports a planning path.
2. Stop after RCA - keep the diagnosis only.
3. Other.
4. Auto-complete.
On opt-out, stop after the summary. Do not write PROBLEM_ANALYSIS.md on opt-out.
On opt-in or Auto-complete, select the smallest fitting planning skill and continue with that skill's contract.

Level Selection

create-a-small-plan: clear root cause, obvious fix shape, few local files, limited risk.
create-a-plan: multi-file fix, external API or dependency behavior, compatibility concerns, or research needed.
create-a-big-plan: cross-system failure, unclear root cause, redesign pressure, or high recoverability risk.

After opt-in, write PROBLEM_ANALYSIS.md in the selected run artifact directory before PLAN_v1.md and pass the RCA summary into the selected planning skill.