Use when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces `docs/plans/YYYY-MM-DD-<feature>.md` with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects \"TBD\", \"TODO\", \"add error handling\", \"similar to Task N\".
Installs into .claude/skills of the current project.
Are you the author of Write Executable Plan?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/kanevry-write-executable-plan-session-orchestrator)
---
name: write-executable-plan
description: "Use when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces `docs/plans/YYYY-MM-DD-<feature>.md` with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects \"TBD\", \"TODO\", \"add error handling\", \"similar to Task N\"."
---
# write-executable-plan
Canonical skill: `skills/write-executable-plan/SKILL.md`
Read that file and follow it exactly. Resolve relative links against `skills/write-executable-plan/`, not this wrapper.
Cursor has no Skill tool. Treat "invoke the write-executable-plan skill" as: Read `skills/write-executable-plan/SKILL.md`.
