workflow-patterns

TDD checkpoints are managed by enforcing sequential task selection, coverage targets, and approval gates before phase progression. The workflow records git commit SHAs and logs deviations to maintain traceability throughout the red-green-refactor cycle.

Test-first development and phase verification are enforced through structured completion gates and manual verification checklists. This approach ensures each task proves correctness with tests and records checkpoint state before progressing to the next phase.

A red-green-refactor cycle integrates with plan.md driven work by aligning task selection with the current phase. It supports test creation, minimum implementation, refactoring, and coverage checks to complete each task methodically.

Yes, you can structure git commits, notes, and plan updates so each TDD task remains traceable and auditable. The workflow controls commit handling by recording commit SHAs and enforcing approval-based checkpoints.

A plan.md file is required for plan-driven work to coordinate task sequencing and checkpoint management. The workflow selects the next pending task in order and keeps implementation aligned with the current phase defined in the plan.

If a task fails phase completion gates, progression is blocked by approval-based checkpoints. Deviations are logged to maintain process discipline, ensuring correctness is proven with tests before moving forward.