implementation-plan

To create a multi-phase implementation plan, generate a Markdown file named IMPLEMENTATION_PLAN_<feature-name>.md. This document structures complex software work by outlining distinct phases with specific goals, tasks, statuses, and quality gates to guide execution.

Tracking cross-team coordination requires a living Markdown document with phased goals and quality gates. By maintaining an implementation plan file in the repository root, teams can document ongoing decisions, track statuses, and manage dependencies across members.

Yes, you can use markdown checklists for project management by generating a structured implementation plan. It captures phased execution details, enabling progress tracking and documentation through a committed Markdown file that outlines tasks and quality gates.

You need a structured implementation plan with quality gates when organizing complex work that requires phased execution, refactoring, or cross-team coordination. It ensures clear goals and tasks are met before progressing through subsequent project phases.

Maintain a living document for project updates by editing the IMPLEMENTATION_PLAN_<feature-name>.md file as work progresses. Committing these updates to the repository reflects current progress, tracks statuses, and records decisions for team members.