plan
Use plan for normal repo changes needing bounded decisions, refinement, and high-priority review before execution; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
npx skills add Optim-Agent/optim-plans --skill 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.
# Plan Read and follow `../optim-plans/SKILL.md`, treating the request as if it named `plan`. Depth: `plan` means 1 to 5 planning questions, at most three refinement rounds, a 600 second reviewer/criticizer timeout, and at most three high-priority comments or questions per round.
What does the plan skill do?
Use plan for normal repo changes needing bounded decisions, refinement, and high-priority review before execution; 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 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.
