big-plan

Solid

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.

AI & Automation 67 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
16
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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.

Details

Author
Optim-Agent
Repository
Optim-Agent/optim-plans
Created
4 days ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

huge-plan

Use huge-plan for open-ended high-risk repo efforts needing websearch during brainstorming and refinement until convergence; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.

67 Updated today
Optim-Agent
AI & Automation Solid

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.

67 Updated today
Optim-Agent
AI & Automation Solid

mini-plan

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

67 Updated today
Optim-Agent