research-plan
openbooklet.com/s/research-planopenbooklet.com/s/research-plan@1.0.0GET /api/v1/skills/research-planBuild execution-ready research plans, experiment proposals, and ablation designs. Prefer invoking via research-workflow. TRIGGER when: user asks for research proposal, experiment plan, ablation design, evaluation roadmap, study design, or after deep-research scoping needs conversion to actionable plan. DO NOT TRIGGER when: evidence gathering needed first (use deep-research), actual experiment launch (use experiment-execution), or paper writing (use paper-writing).
Execute AI/ML experiments locally or remotely with environment, runtime, and logging controls. Prefer invoking via research-workflow. TRIGGER when: user asks to run/launch/start/resume/monitor a training job, evaluation, or benchmark, or a plan is ready for execution, or experiment needs rerun/recovery. DO NOT TRIGGER when: research investigation only (use deep-research), planning without execution (use research-plan), or env setup without launch (use project-context).
Escalate critical decisions to a human with options, tradeoffs, and recommendation. TRIGGER when: major safety risk, high irreversible impact, large GPU spend, destructive data ops, shared-memory publication, or hard blockers requiring human approval. DO NOT TRIGGER when: routine confirmations handled by run-governor, or low-stakes reversible actions.
Govern run-level execution policy: mode selection, run_id, directory layout, stage reporting, safety allowances. TRIGGER when: starting a non-trivial research task (set mode + run_id), switching local/remote target, creating a new run, or mode-aware policy decisions needed. DO NOT TRIGGER when: trivial single-step tasks, pure info queries, or run already initialized with no policy change needed.
Auto-indexed from TenureAI/PhD-Zero
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.