flow-work

To execute a markdown plan with Git-backed task tracking, load your plan file and follow a phase-based workflow that processes steps in order, enforces completion, and commits progress with traceable state.

Phase-based plan execution for software feature development is a structured workflow that breaks implementation into sequential phases, enforcing task completion, running quality checks, and committing progress to Git at each stage.

You can track Beads epics through a Git workflow by providing a Beads ID as input, which the system processes through structured phases to execute tasks, run tests, and commit verifiable progress with full traceability.

No special setup is required to run plan-driven task execution alongside Git beyond having Git installed, as the workflow directly leverages your existing repository state to track progress and commit completed phases.

Git enforces quality checks during plan execution by integrating test and lint runs into the phase-based workflow, ensuring tasks pass validation before progress is committed and marked as complete.

The best way to prevent context drift when implementing from a spec is to use a structured plan execution workflow that enforces sequential phase completion, tracks progress in Git, and validates each step before committing.