deep-research-plan
openbooklet.com/s/deep-research-planopenbooklet.com/s/[email protected]GET /api/v1/skills/deep-research-planUse 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.
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.
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.
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.
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.
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.
Alias for search-and-plan when external research should inform a repo-change plan before implementation.
Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
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.
Auto-indexed from Optim-Agent/optim-plans
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.