Writing Implementation Plans
Write plans an engineer who never saw the codebase can execute: exact files, interfaces, tests, step granularity, self-review
- What
- Write plans an engineer who never saw the codebase can execute: exact files, interfaces, tests, step granularity, self-review
- Cost
- Free
- Needs
- a spec or requirements document to plan from; a project the plan targets. Companion execution skills: obra-subagent-driven-development or executing-plans.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a plan-writing skill for an implementer who has never seen this codebase or this spec: document only what they cannot know — which files, which exact names and signatures, which values from the spec, which tests prove each task — and leave everything else to their idiomatic judgment. It prescribes the plan's structure: a mandatory header (goal, architecture, tech stack, spec path, Global Constraints with exact values, Review Focus listing the five uncovered input classes most likely to bite), a file structure that locks decomposition decisions, right-sized tasks where each ends in an independently testable deliverable, one-action steps with checkable results, and a self-review pass (spec coverage, step scan, type consistency, proportion — a plan longer than the code it describes has written the code instead). It ends with the execution handoff: the human reviews the plan, then picks subagent-driven or native execution. By @obra, listed here with credit to its creator. Honest caveats: it's a writing method, not automation — plans land in `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md` and are executed by the sibling subagent-driven-development or executing-plans skills; the plan itself must never contain what a step's signature and tests already determine. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Writing Implementation Plans is a free Muse skill for writing plans an engineer who never saw the codebase can execute. It specifies exact files, interfaces, tests and step granularity, with self-review built in. Clear plans like these reduce back-and-forth, prevent misread intentions and let implementation start immediately.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bb92a77Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a spec or requirements document to plan from; a project the plan targets. Companion execution skills: obra-subagent-driven-development or executing-plans. Install "Writing Implementation Plans" for me. It writes plans an engineer who never saw the codebase can execute: exact files, interfaces and signatures, tests per task, one-action steps, and a self-review pass. Repository: https://raw.githubusercontent.com/obra/superpowers/bb92a77741419a4ab5f06e711a283343f1ada0c3/skills/writing-plans/SKILL.md Pinned version: install the code at commit bb92a77741419a4ab5f06e711a283343f1ada0c3 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "obra-writing-plans". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- bb92a77 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.