writing-plans

Writing Plans

Writing Plans is an agent skill from Superpowers: your agent turns a spec into a step-by-step implementation plan with exact files, signatures and tests, before touching code.

Checked by CookiesForAI on : license and last change of the skill re-read from GitHub.

Written by

Install Writing Plans

Install only this skill with the skills CLI

Terminal
npx skills add obra/superpowers --skill writing-plans

Or, in Claude Code, install the whole Superpowers plugin from Anthropic's official marketplace

Agent chat
/plugin install superpowers@claude-plugins-official

Or paste this into your coding agent: Install the agent skill writing-plans from github.com/obra/superpowers. Checked by CookiesForAI on : license and last change of the skill re-read from GitHub. A skill can include scripts that run on your computer, so read its source first.

What Writing Plans does

Writing Plans is one of the skills in Superpowers, Jesse Vincent's open-source method for AI coding agents. It loads once a multi-step task has a spec or a set of requirements and no code has been written yet. The agent writes the plan for an engineer who has never seen the codebase or the spec, recording the decisions that engineer could not make alone: the files to touch, the names and signatures to use, the values taken from the spec, and the tests that prove each task.

Writing Plans saves plans to docs/superpowers/plans/ unless you prefer another place. Each starts with a header naming the goal, architecture, tech stack and spec, a Global Constraints section with values copied from the spec, and a Review Focus list of failure modes no test covers yet. Every task lists its exact files and the interfaces it consumes and produces, split into small checkbox steps: write the failing test, run it, implement, run it again, commit.

Before Writing Plans hands over, the agent checks the plan against the spec for requirements with no task, steps that decide nothing, names that differ between tasks, and a plan far longer than its spec. It then asks you to review the plan and choose how to run it: Subagent-Driven Development, where a fresh subagent does each task, or native execution with Executing Plans. An isolated worktree, if used, comes from Using Git Worktrees.

When to use Writing Plans

  • You have a spec or design and want it broken into small, testable tasks before any code is written.
  • You plan to hand the work to subagents or another session and need a plan that stands on its own.
  • Your agent's plans say things like "handle edge cases" and you want exact files and tests instead.

When to pick something else

  • You do not have a spec or design yet: start with Brainstorming.

Which agents Writing Plans works in

Jesse Vincent documents Writing Plans for Claude Code, Codex (app and CLI), Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Antigravity, Devin CLI, Factory Droid, Grok Build CLI, Kimi Code, Pi, Qwen Code, Hermes Agent, Muse. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on ). See where each agent looks for skills.

Superpowers is written in Claude Code's vocabulary (subagent dispatch, todos, the Skill tool) and ships tool mappings for Codex, Gemini CLI, Pi, Antigravity, Hermes Agent and Muse. Installed as the full plugin, a session-start hook loads Using Superpowers so the agent reaches for skills on its own; one skill installed with the skills CLI gets no hook and may point to sibling skills you do not have.

Writing Plans license

Writing Plans is published under MIT.

More from Jesse Vincent

Lists that include writing-plans