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.
SkillScore45Maintained
Automatic
◆Coding pack
Last verified 8/24/2026
What it changes
Passed 5 of 12 test cases with the skill, and 4 of 12 without it.
Without skill32%
With skill45%
Checks it passed that the model alone missed
The second-to-last choice is explicitly Other.
The request passes the PROBLEM_ANALYSIS.md artifact intent.
The 5 Whys breakdown terminates at unknown due to missing crash logs.
and 6 more in the full report
6 fixed4 passed either way9 still failing3 broke
Pass-rate lift
+14 pp
Tokens
+7%
Agent turns
0%
Response time
-30%
Model gemini-3.6-flashMeasured 8/24/2026v110 of 22 cases passed with skill · 12 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
After inspecting the database connection timeout issue in `config/database.yml`, we decided to opt in to generating a plan. What is the required sequence for writing `PROBLEM_ANALYSIS.md` relative to `PLAN_v1.md`?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies writing PROBLEM_ANALYSIS.md before PLAN_v1.md in the artifact directory.
Passed
Passed
The response mentions recording the first controller-backed planning question before creating PROBLEM_ANALYSIS.md.
Missed
Passed
case-14 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md34 linessingle file
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
Inspect available evidence first: repo files, logs, tests, command output, or 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; do not invent a cause.
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.
On opt-out, stop after the summary. Do not write PROBLEM_ANALYSIS.md on opt-out.
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.
Pass the original problem, RCA summary, evidence, and PROBLEM_ANALYSIS.md artifact intent as the planning request. The selected planning skill must initialize controller state and present and record its first controller-backed planning question before PROBLEM_ANALYSIS.md is written.
After opt-in, selected planning skill first controller-backed planning question recording, and selected run artifact_dir availability, write PROBLEM_ANALYSIS.md in that artifact_dir before PLAN_v1.md.