Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
A skill your agent uses when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria.
Install Write Plan
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .claude/skills/write-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .claude/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .agents/skills/write-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .agents/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .cursor/skills/write-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .cursor/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git --path skills/60-regisely-superpapers/skills/write-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .gemini/skills/write-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .gemini/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .github/skills/write-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .github/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills write-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/60-regisely-superpapers/skills/write-plan .opencode/skills/write-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-plan" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/60-regisely-superpapers/skills/write-plan into .opencode/skills/write-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-plan- GitHub stars
- 4.5k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,136 words
- Files
- 1
- Skills in repo
- 369
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria.
- Works in 8 steps: Literature → Collection → Preparation → …
- A research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks
- SKILL.md covers Overview, When to Use, Prerequisites and Mandatory Steps, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Write Plan is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Use when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria. Produces a research execution plan organized in canonical research phases — collection, preparation, analysis, robustness, writing, submission.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning. The repository describes itself as: 🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库，覆盖8大社会科学学科的实证研究。CoPaper.AI…
When your agent uses it
- A research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks
- Verification criteria
Example prompts
- “/write-plan”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- Literature
- Collection
- Preparation
- Exploratory Analysis
- Main Analysis
- Robustness
- Writing
- Submission
What it can do on your machine
Read from SKILL.md and the folder at commit 9fa87d8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write Plan loads about 2.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,136 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,136 words (~2,318 tokens).
“This skill writes a detailed, research-structured implementation plan from an approved design spec. It begins by invoking academic-baseline as the standing policy layer for the planning session. The plan is organized in research phases — not software phases — and…”
- name
- write-plan
Files
Just SKILL.md in skills/60-regisely-superpapers/skills/write-plan of brycewang-stanford/Auto-Empirical-Research-Skills.
Open the folder on GitHubat commit 9fa87d8
Compare with similar skills
Write Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Plan this skillbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 102k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 56 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from brycewang-stanford/Auto-Empirical-Research-Skills
All 369 skills in this repoLatex Paper En
brycewang-stanford/Auto-Empirical-Research-Skills
English LaTeX academic paper assistant for existing .tex projects.
Bayesian Workflow
brycewang-stanford/Auto-Empirical-Research-Skills
Opinionated Bayesian modeling workflow with PyMC and ArviZ. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
Five Questions
brycewang-stanford/Auto-Empirical-Research-Skills
Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.
Kaggle Research
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when a research task needs reproducible Kaggle discovery, metadata inspection, bounded public-data downloads, competition or kernel discovery, model discovery, or an…
Latex Thesis Zh
brycewang-stanford/Auto-Empirical-Research-Skills
Chinese LaTeX thesis assistant for existing .tex degree thesis projects (XeLaTeX/LuaLaTeX/latexmk).
Obsidian Project Memory
brycewang-stanford/Auto-Empirical-Research-Skills
This skill should be used when the user asks to maintain an Obsidian knowledge base for a research project, import an existing research repository into Obsidian, keep project memory or daily notes…
Related
Categories
Questions about Write Plan
What does Write Plan do?
A skill your agent uses when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria. Write Plan is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Use when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria.
When should I use Write Plan?
Write Plan fits situations like: A research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks; verification criteria.
How do I install Write Plan in Claude Code?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a claude-code`. Or copy the skill folder (skills/60-regisely-superpapers/skills/write-plan in brycewang-stanford/Auto-Empirical-Research-Skills) into .claude/skills/write-plan in your project. Claude Code loads it when a task matches its description.
How do I install Write Plan in Codex?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a codex`. Or copy the skill folder (skills/60-regisely-superpapers/skills/write-plan in brycewang-stanford/Auto-Empirical-Research-Skills) into .agents/skills/write-plan in your project. Codex loads it when a task matches its description.
Can I use Write Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-plan, .gemini/skills/write-plan, .github/skills/write-plan and .opencode/skills/write-plan in your project.
What does Write Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Write Plan is instructions for the agent only.
Does Write Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write Plan use?
Write Plan has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Write Plan use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write Plan?
Skills that share tags, products or a category with Write Plan: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 102k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Plan?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Auto-Empirical-Research-Skills, which has 4,517 GitHub stars. The repository holds 369 skills in this directory. The repository was last updated on October 5, 2026.
Source: brycewang-stanford/Auto-Empirical-Research-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.