mcpbeat

Search And Plan

optim-agent/search-and-plan

Use when external research should inform a repo-change plan before implementation; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.

585 tokens
context cost
the whole folder, loaded on every use
1
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 search-and-plan

The instruction itself

4 sections, as written by the author

Search And Plan

Research first; planning and execution still follow ../optim-plans/SKILL.md.

Required Flow

  • Read and follow ../optim-plans/SKILL.md, preserving explicit mini-plan, small-plan, plan, big-plan, and huge-plan routing.
  • Inspect the target Git repo read-only before asking product questions.
  • Initialize or resume the optim-plans controller before external research.
  • Perform read-only initial research. Prefer agent-reach when available; if missing, give one sentence of install guidance, do not install agent-reach or any other tool before execution approval, and continue with fallback search/repo evidence.
  • Ask the first evidence-informed question as a controller-backed optim-plans choice prompt, and submit/record that answer through the controller before writing refs.
  • Only after that recorded controller answer, write sources and REF_ANALYSIS.md under docs/optim-plans/YYYY-MM-DD-topic/refs/search-and-plan/<topic>/.
  • Ask any later product questions only after refs are persisted.
  • Continue into the selected optim-plans level: PLAN_v1.md, refinement, immutable execution approval, execution, validation, controller verification, and integration gates.

Research Contract

  • Keep a 3-7 high-signal source pack; if fewer than 3 credible sources exist, record the gap instead of padding with weak sources.
  • Record attempted queries, attempted backends, backend failures with reasons, why sources were insufficient, and then continue from repository evidence.
  • Backend failure fallback is valid only when the failure reason is recorded.
  • Do not write pre-execution ./refs/ files; refs live only under the run artifact path above.
  • Do not require a strict source manifest before planning.

REF_ANALYSIS.md

Use these sections exactly:

  • ## Sources
  • ## Findings
  • ## Adoptable ideas
  • ## Risks/not-applicable points
  • ## Evidence gaps
  • ## Candidate user decisions

Every adoptable idea must be presented as an evidence-backed optim-plans choice prompt and recorded through the controller before it can be included in any plan.

How to use it

Copy the folder

Take optim-agent/search-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.