write-plan
/write-plan
Stage 3a (Build) - turn spec.md into plan.md, an ordered, testable implementation plan with files to touch, steps, tests per step and rollback. Use after the spec is written, when the user says "plan the implementation", "break this down", or at the start of /sdlc-loop:build. Never edits source code.
- Author
- Marcdaou ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Stage 3a (Build) - turn spec.md into plan.md, an ordered, testable implementation plan with files to touch, steps, tests per step and rollback. Use after the spec is written, when the user says "plan the implementation", "break this down", or at the start of /sdlc-loop:build. Never edits source code.
Triggers from the description
Original author description
Stage 3a (Build) - turn spec.md into plan.md, an ordered, testable implementation plan with files to touch, steps, tests per step and rollback. Use after the spec is written, when the user says "plan the implementation", "break this down", or at the start of /sdlc-loop:build. Never edits source code.
How it works
SKILL.md has no level-two headings · 35 lines, 275 words
SKILL.md preview
--- name: write-plan description: Stage 3a (Build) - turn spec.md into plan.md, an ordered, testable implementation plan with files to touch, steps, tests per step and rollback. Use after the spec is written, when the user says "plan the implementation", "break this down", or at the start of /sdlc-loop:build. Never edits source code. --- # Write plan.md "Nothing is implemented without an accepted plan." The plan exists so the human can catch a wrong approach in two minutes instead of in a 600-line diff. So make it short, concrete and reviewable. 1. Read spec.md and design.md, then inspect every file you intend to touch (do not plan against files you haven't opened). **Check the spec against the current code**: list requirements that are already met (no change) and bugs the spec didn't mention - this is often where the real work is. - If the repo lacks a test runner or linter, still plan the tests; say the builder may add `vitest` as a devDependency (the tester adds lint). - New migration: next number after the highest in `<app.migrationsDir>`. - If a migration adds something the frontend calls, plan a **fallback** for when it isn't applied yet (preview and production often share one database and agents never apply migrations), or flag it as a risk the human must decide. 2. Write `plan.md`: ```markdown # Plan: <KEY> Branch: <KEY>-<slug> ## Files | File | Change | Why (spec req ID) | ## Steps 1. <small, verifiable step> - verify: <command or check> 2. ... ## Tests to add | Test file (or "Manual on preview") | Covers req ID | ## Migrations <new file <app.migrationsDir>/NNNN_<name>.sql, or "none"> ## Rollback <how to revert: revert PR; down-migration SQL if any> ## Risks / things I'm unsure about ``` 3. Keep steps in an order where the app builds after each one. 4. Do not edit anything outside the work folder. Update status.json (`stage: "build"`, `approved.plan: false`) and return ending with `NEEDS_APPROVAL: docs/work/<...>/plan.md`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Marcdaou/claude-plugins | 100 | MIT |
| j0hanz/j0hanz-marketplace | 100 | MIT |
| jelvodev/yaap | 100 | MIT |
| trihuynh-agilityio/workez | 100 | MIT |
| existential-birds/beagle | 100 | Apache-2.0 |
| Ovich/charrette | 90 | MIT |
Database snapshot: 13.11.2026 · package version e708fa10cf89 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95ro-spec
Turn a game design idea into an implementation spec for an rAthena server - requirements, feasibility layers, files to touch, data, acceptance tests, risks. Use when the user says "write a spec", "plan this feature", "how would we build X", "break this down", or hands a design… - 100writing-plans
Turns an approved spec or design doc into an implementation plan of vertical-slice tasks, each with exact files, interfaces, failing tests, commands, and expected output, ordered so the first slices deliver most of the value, and stress-tested with a pre-mortem. Use when a spec,… - 100plan
Use when breaking down a Beat change spec into tasks — not for spec creation or implementation - 100plan-work
Break down an issue or task into concrete implementation steps with file locations, code changes, and acceptance criteria. Use when the user asks to "plan the implementation", "break down this task", "create an implementation plan", or needs a structured plan before coding. - 95write-implementation-plan
Use this skill when the user says 'plan before coding', 'write an implementation plan', 'implementation_plan.md', 'propose changes first', 'what files would you change', 'plan this feature', or when a coding task touches multiple files/modules and approval is expected before… - 100implementation-planning
Break down specifications into executable implementation plans with TDD integration. Use when asked to "create plan", "break down tasks", "implementation roadmap", "規劃實作", "拆解任務", "執行計畫", or need step-by-step implementation guidance with test strategies and impact analysis. Use…