Directory · Claude Skills

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.

★ 156 Synced 4 days ago View SKILL.md

At a glance

Plugin install
Install /plugin marketplace add Optim-Agent/optim-plans /plugin install big-plan
Can use Not declared by the author

Also in Optim-Agent/optim-plans

View the repo

MUST USE when investigating a bug, CI failure, test failure, regression, incident, broken behavior, root cause, RCA, or debug-why problem be...

Use huge-plan for open-ended high-risk repo efforts needing websearch during brainstorming and refinement until convergence; exclude direct...

Use mini-plan for subtle low-risk repo changes needing one alignment question before execution; exclude direct implementation-only, factual/...

MUST USE when a user asks to plan, brainstorm, design, scope, review, or evaluate a repo change before implementation; do not use for direct...

Use plan for normal repo changes needing bounded decisions, refinement, and high-priority review before execution; exclude direct implementa...

Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is avail...

Use when the user asks Codex to review a repository for improvement opportunities, feature inspiration, roadmap ideas, or implementation can...

Use small-plan for small repo changes needing up to three intent checks and exactly one refinement round; exclude direct implementation-only...