write-plan
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.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Write Plan ## Overview 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 every task has an expected artifact, verification criterion, and explicit skill routing. `replication-driven-
What does the write-plan skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill write-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.