writing-plans

Implementation plans break down features into bite-sized tasks (2-5 minutes each) with exact file paths, complete code examples, precise commands, and testing steps. This Skill generates comprehensive plans assuming zero domain knowledge, saving output to docs/plans/YYYY-MM-DD-<feature-name>.md for seamless handoff to engineers.

A development plan for TDD and integrations must include concrete file changes, unit and integration tests, documentation updates, DRY and YAGNI principles, exact commands with expected outputs, commit guidance, and verification criteria. This ensures consistent execution across architectural changes and feature scoping.

Yes. Implementation plans handle architectural changes by decomposing them into granular, sequential tasks with file paths, code examples, and testing cycles. Plans recommend parallel execution tracks when appropriate and provide clear handoff points for complex integrations.

Task breakdown uses bite-sized granularity (2-5 minute cycles) with TDD workflows, exact file modifications, and commit instructions. Each step includes expected outputs and verification criteria, enabling both sequential execution for simpler features and parallel decomposition for larger efforts.

Executable plans eliminate confusion and rework by providing zero-context documentation: exact file paths, complete code examples, precise terminal commands, testing steps, and verification criteria. Vague plans lack this specificity, causing delays for engineers unfamiliar with the codebase.

Yes. Plans satisfy project management workflows by documenting implementation steps, dependencies, and testing phases with concrete examples and commit guidance. They serve as reference documentation for design approval and team handoff, supporting both planning and execution phases.