plan

Solid

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.

AI & Automation 46 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

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

Skill Content

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

Details

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

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

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.

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

46 Updated today
Optim-Agent
AI & Automation Solid

optim-plans

MUST USE when a user asks to plan, brainstorm, design, scope, review, or evaluate a repo change before implementation; do not use for direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.

46 Updated today
Optim-Agent