Writing Implementation Plans

What it does

Transforms a high-level spec into a detailed, zero-context implementation plan that an unfamiliar developer can follow. The plan specifies exact files to change, test code examples, commands to run, and a sequence of small tasks (2–5 minute steps) with expected outcomes. It enforces no placeholders (no TODOs/TBD) and includes a mandatory self-review checklist.

When to use it

Use after brainstorming or spec approval, for multi-step feature work, larger refactors, or when handing work to subagents or human engineers. Skip for trivially small tasks (<3 files). It’s ideal before coding begins and when you need reproducible, reviewable plans saved under docs/plans/active/.

What's included

• Scripts: none bundled (has_scripts=false)
• References: may include reviewer prompts (sibling plan-document-reviewer-prompt.md)
• Instructions: detailed templates for plan headers, task decomposition, test-first steps, execution handoff questions, and self-audit rules to eliminate placeholders. The skill defines exact file path conventions and commit guidance.

Compatible agents

Designed for OpenCode-style agents and developer assistants operating with Gemini, Claude, or similar toolchains; useful for subagent-driven workflows and inline executors.