workflow-tdd-plan-plan

To generate a TDD plan, the workflow orchestrates a 6-phase session that converts a feature description into IMPL_PLAN.md, IMPL-reek.json task files, and TODO_LIST.md, structuring each task with Red-Green-Refactor steps. It analyzes context and test coverage to enforce a test-first approach.

A TDD compliance report is a TDD_COMPLIANCE_REPORT.md generated in verify mode that validates task chain correctness and TDD phase completeness. It includes a binding quality gate decision with recommended next actions based on collected coverage metrics.

To resolve code-plan conflicts, the workflow runs conflict analysis and applies resolution strategies only when detected conflict risk is medium or high. It updates planning notes and resolution artifacts to ensure the generated task metadata remains consistent.

Yes, every generated implementation task must contain exactly three internal TDD steps: red, green, and refactor. The tasks also include proper iteration limits for green test-fix cycles to ensure dependency-aware task structuring.

The best way to validate TDD phase completeness is running the workflow's verify mode, which checks task chain correctness and runs coverage metrics. It outputs a TDD compliance report with a binding quality gate decision to prevent shipping code without failing tests first.