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.
EnglishUse 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.
EnglishMUST 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.
EnglishUse when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
EnglishUse 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.
EnglishUse when external research should inform a repo-change plan before implementation; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
EnglishIncludes Analyze and Plan, Deep Research Plan, Optim Plans, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
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.
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.
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.
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.
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.
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.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Analyze and Plan skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.