big-plan
Use big-plan for broad or risky repo changes needing codebase inspection, websearch, and deeper refinement; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
npx skills add Optim-Agent/optim-plans --skill big-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.
# Big Plan Read and follow `../optim-plans/SKILL.md`, treating the request as if it named `big-plan`. Depth: `big-plan` means 5 to 10 planning questions, required brainstorming websearch, at most five refinement rounds, an 1800 second reviewer/criticizer timeout, and at most five high-priority comments or questions per round.
What does the big-plan skill do?
Use big-plan for broad or risky repo changes needing codebase inspection, websearch, and deeper refinement; 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 big-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.