writing-plans

Implementation plans break down features into bite-sized tasks with exact file paths, complete code examples, and verification steps. This Skill generates comprehensive plans that specify which files to create or modify, include full code blocks, define tests, and provide git-commit instructions—enabling junior or new engineers to execute tasks independently without constant supervision.

An implementation plan includes a one-sentence goal, 2–3 sentences on architecture and approach, the tech stack, and numbered tasks. Each task specifies files to create or modify with exact paths, line ranges for edits, complete code examples, test files, and verification commands. Plans are saved with date-stamped filenames in docs/plans.

Yes. Implementation plans eliminate ambiguity by providing step-by-step guidance with precise file locations and code examples. Junior engineers can execute 2–5 minute tasks sequentially without needing deep codebase knowledge, reducing onboarding time and supervision overhead while ensuring consistent, correct execution.

Implementation plans enforce DRY (Don't Repeat Yourself), YAGNI (You Aren't Gonna Need It), and TDD (Test-Driven Development) principles throughout task definitions. Each task includes test specifications and verification commands, ensuring code quality from the start rather than requiring post-implementation review cycles.

Implementation plans go beyond task lists by providing exact file paths, complete code blocks ready to copy, test definitions, and verification commands. Basic lists state what to do; implementation plans show exactly how to do it, where to do it, and how to verify it worked—eliminating guesswork for engineers unfamiliar with the codebase.