writing-plans

Implementation plans break complex features into small, ordered tasks specifying exact files to create or modify, alongside required tests and verification steps. This structured approach prevents missed details and reduces guesswork during execution.

Create task guidance for delegated work or subagents by producing detailed, copy-pasteable implementation plans. These plans include exact file paths, tests, commands, commit steps, and TDD alignment, providing enough context for another developer or subagent to follow with minimal context.

The best way to plan a multi-step software refactor is to generate a task-by-task roadmap. This roadmap identifies exact files to modify, necessary tests, and verification steps, ensuring the refactor aligns with DRY and YAGNI principles while remaining easy to review.

Yes, test-driven development aligns directly with step-by-step implementation plans. The planning process integrates TDD by defining specific tests and verification points for each task, ensuring code changes are validated before moving to the next step.

Yes, you can use structured planning for bug fixes and documentation tasks. The approach decomposes any multi-step work into ordered tasks with exact file paths and verification steps, making it suitable for any work that benefits from structured planning.

You need to specify exact file paths in an implementation plan to ensure careful handoff and reduce guesswork. Identifying exact files to create or modify, along with associated tests and commands, allows another developer or subagent to execute the task with minimal context.