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.
npx skills add Optim-Agent/optim-plans --skill search-and-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Search And Plan Research first; planning and execution still follow `../optim-plans/SKILL.md`. ## Required Flow 1. Read and follow `../optim-plans/SKILL.md`, preserving explicit `mini-plan`, `small-plan`, `plan`, `big-plan`, and `huge-plan` routing. 2. Inspect the target Git repo read-only before asking product questions. 3. Initialize or resume the optim-plans controller before external research. 4. 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. 5. 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. 6. 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>/`. 7. Ask any later product questions only after refs are persisted. 8. Continue into the selected optim-plans level: `PLAN_v1.md`, refinement, immutable execution approval, execution, validation, controller verification, and
- Required Flow
- Research Contract
- REFANALYSIS.md
What does the search-and-plan skill do?
Use when external research should inform a repo-change plan before implementation; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
How do I install it?
Run `npx skills add Optim-Agent/optim-plans --skill search-and-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Optim-Agent/optim-plans, a repository with 288 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.