plan-writing

To structure tasks for clear execution, you need a plan template that breaks down multi-team initiatives into phases, atomic tasks, explicit ownership, and dependencies. This approach enforces a repeatable format for ongoing project visibility.

The best way to manage project dependencies and ownership is by creating a structured PLAN file template. This format enforces atomic task breakdown with explicit assignees and maps dependencies across project phases for team coordination.

To start writing a project plan, create a new PLAN file at docs/PLAN-{slug}.md. Begin outlining the project phases and tasks using the enforced template structure to capture ownership and dependencies.

To keep project plans current during ongoing task coordination, follow the provided DO and DON'T practices for plan maintenance. This enforces an update procedure to ensure task breakdowns and dependencies remain accurate.

Yes, you can use atomic task breakdown for multi-team project planning. The plan template enforces atomic tasks with explicit dependencies and assignees, ensuring clear execution and improved project visibility across teams.