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.

Jump to install

Repository: Optim-Agent/optim-plans
Last source activity: August 9, 2026 at 13:23
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Optim-Agent/optim-plans --skill diagnose-before-plan

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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:

Create the scoped fix plan - recommended when evidence supports a planning path.
Stop after RCA - keep the diagnosis only.
Other.
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.