wz:writing-plans

To turn approved designs into an execution plan, you draft an ordered, task-based sequence detailing concrete tasks, subtasks, acceptance criteria, verification steps, and cleanups for phase-driven work.

The best way to structure phase-driven project plans is by generating an ordered sequence of explicit tasks, milestones, and acceptance criteria, ensuring every phase has defined verification steps and cleanups before moving forward.

When no active run exists, you save executable project plans as standalone markdown files in the docs/plans directory using the YYYY-MM-DD-<topic>-implementation.md naming format.

Yes, you can iteratively validate a task management plan with stakeholders using a Plan Review Loop, which allows you to continuously refine the ordered tasks and acceptance criteria based on stakeholder feedback before execution begins.

Yes, you need clear direction, research findings, and design approvals in place before drafting an implementation plan, because the process converts these finalized inputs into an actionable, execution-grade sequence of tasks.

When integrated into an active project run, execution plans are saved directly under the .wazir/runs/latest/clarified/ directory structure to maintain continuity with the active workflow.