mcpbeat Sign in

Analyze And Plan Agent 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 implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.

718 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
264
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Optim-Agent/optim-plans --skill analyze-and-plan

The instruction itself

4 sections, as written by the author

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.

Level Selection

  • mini-plan: single-file, low-risk, clear root cause, obvious fix.
  • small-plan: a few local files or behavior checks, limited risk.
  • plan: normal multi-file fix with several decisions.
  • big-plan: architecture boundary, external API/dependency, compatibility, or websearch risk.
  • huge-plan: open-ended or cross-system issue where the RCA points to redesign.

PROBLEM_ANALYSIS.md

Include:

  • Original problem
  • Evidence inspected
  • RCA summary
  • 5 Whys, ending early with unknown when evidence stops
  • Suspected root cause
  • Planning level selected and why

Auto-complete may opt into planning, but Auto-complete cannot approve execution.

Other skills for the same job

different authors, same section of the catalogue
Workflow Patterns
by ComeOnOliver
×2

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

6k tokens
Iso Standards Readiness
by K-Dense-AI
×1

Prepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, scope of accreditation, traceability, CAPA, external-provider controls, or bounded local evidence manifests, and when separating ISO certification from laboratory accreditation, FDA QMSR inspection, CLIA certification, MDSAP, and EU MDR/IVDR evidence boundaries. Not for legal applicability, compliance, certification, or accreditation decisions; contains no clause text.

67k tokens scripts
Statistical Power
by K-Dense-AI
×1

Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers closed-form power for t-tests, ANOVA, proportions, correlations, chi-square, and regression, plus simulation-based (Monte Carlo) power for designs with no formula — logistic/Poisson regression, mixed models, cluster-randomized trials, survival, and interactions. Use this skill even when the request only mentions an effect size, alpha, or "80% power" without saying "power analysis" explicitly. For laying out the study (randomization, blocking, factorial/DOE, crossover, sequential designs) use experimental-design; for analyzing data already collected and reporting it use statistical-analysis.

13k tokens scripts
General Figure Guide
by BioTender-max
×1

Universal QA checklist for generated scientific plots: overlapping labels, clipped text, missing axes/legends, overcrowded data, and cross-journal resolution/format guidance.

2k tokens
Nerdzao Elite
by ComeOnOliver
×1

Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.

3k tokens
Pinchbench
by ComeOnOliver
×1

Run PinchBench benchmarks to evaluate OpenClaw agent performance across real-world tasks. Use when testing model capabilities, comparing models, submitting benchmark results to the leaderboard, or checking how well your OpenClaw setup handles calendar, email, research, coding, and multi-step workflows.

2096k tokens scripts
Workflow Patterns
by ComeOnOliver
×1

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

6k tokens
Powertoys Verification
by microsoft
vendor

Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by building + sideloading the module when the PR isn't in the build yet (unmerged or not-yet-released). Drive each item via UIA invoke / Named Events / settings.json edits / clipboard / GPO / SendInput, and emit a structured PASS / FAIL / BLOCKED verdict per item with evidence (FAIL distinguishes product defects from stale/ambiguous checklist items). Use when asked to verify a module checklist, validate a PR, sign off a release/hotfix's PRs, or QA installed/sideloaded PowerToys bits. Combines generic winapp ui mechanics (references/winapp-ui-testing.md) with PT-specific recipes, per-scenario playbooks (references/scenarios/), and the helper .ps1 files shipped with this skill.

86k tokens scripts

How to use it

Copy the folder

Take optim-agent/analyze-and-plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.