Optim-Agent
UserHuman-in-the-loop planning plugin for Claude and Codex: turn ideas into reviewed Markdown plans, record decisions, enforce explicit execution gates, and provide tested controller primitives for safer agent workflows.
Categories
Indexed Skills (15)
reference-before-plan
Research references before creating a Prime Agent plan. Use when repo-change planning needs downloaded projects, articles, papers, docs, per-reference analysis, adoption questions, language settings, and reviewer or criticizer subagents; exclude direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.
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.
deep-research-plan
Use deep-research-plan for repo-change plans needing downloaded projects, articles, or papers, per-reference analysis, graphify JSON, and stronger-than-huge planning; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
search-and-plan
Use when external research should inform a repo-change plan before implementation; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
review-and-plan
Use when the user asks Codex to review a repository for improvement opportunities, feature inspiration, roadmap ideas, or implementation candidates before planning changes; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
analyze-and-plan
MUST USE when investigating a bug, CI failure, test failure, regression, incident, broken behavior, root cause, RCA, or debug-why problem before deciding whether to create an optim-plans solution plan; do not use for ordinary feature ideas, vague product planning, direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
create-a-big-plan
Create a large Prime Agent plan before implementation. Use for open-ended or high-risk repo efforts needing 10 or more planning questions, web research, reviewer or criticizer subagents, and refinement until convergence; exclude direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.
create-a-plan
Create a researched Prime Agent plan before implementation. Use for broad or risky repo changes needing 5 to 10 planning questions, web research, reviewer or criticizer settings, and bounded refinement; exclude direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.
create-a-small-plan
Create a small Prime Agent plan before implementation. Use for small scoped repo changes needing 1 to 3 planning questions and one reviewer or criticizer refinement pass; exclude direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.
diagnose-before-plan
Diagnose failures before creating a Prime Agent plan. MUST USE for bugs, CI failures, test failures, regressions, incidents, broken behavior, root cause, RCA, or debug-why requests before deciding whether to plan; preserve language, reviewer, and criticizer settings in .git/optim-plans; exclude ordinary feature planning, direct implementation-only, factual/explanation, trivial command-only, or explicit no-plan requests.
resume-previous-plan
Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
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.
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.
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.
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.