writing-plans

To create an implementation plan, generate a task-by-task roadmap covering architecture, API design, testing, and delivery steps. This approach reduces scope creep by enforcing DRY, YAGNI, and TDD principles before coding begins.

Enforcing test-driven development during task planning involves generating detailed roadmaps that explicitly integrate TDD principles. By outlining architecture and test steps before coding, you ensure testable, maintainable plans and avoid unnecessary work.

Yes, implementation planning applies to multi-step software feature development across teams. It saves plans to a standardized path, docs/plans, which facilitates easy onboarding, cross-team review, and execution handover.

Using a dedicated worktree workflow involves creating comprehensive, executable implementation plans prior to coding. This ensures precise roadmaps for architecture and delivery, keeping multi-step feature development isolated and organized.

Software development suffers from scope creep and miscommunication when comprehensive implementation plans are not created before coding. Generating executable, task-by-task roadmaps with enforced best practices prevents these issues.