task-review

You can validate your task list against TDD structure and source specifications by cross-referencing individual tasks for determinism, verifiability, and atomicity. This process ensures correct RED-GREEN pairing and identifies requirement coverage gaps before implementation begins.

Task determinism and verifiability in development workflows mean that each task is atomic, produces a clear outcome, and can be objectively tested. This ensures tasks are well-defined and adhere to structured development patterns like TDD.

To check requirement coverage for a feature spec or PRD, cross-reference your task list against the source specification. This identifies implementation gaps by ensuring every interface, error scenario, and test plan has a corresponding task.

You need task validation before starting development on a new feature to ensure every requirement from your feature spec has a corresponding implementation and test task. This prevents costly errors during implementation by verifying TDD structure and requirement coverage.

Yes, you can use TDD task review for quality assurance on an existing fix plan. It analyzes the fix plan against the spec file to verify TDD RED-GREEN pairing, requirement coverage, and adherence to development best practices before coding begins.

A limitation of validating task lists before coding begins is that it only identifies implementation gaps in the plan against source specifications. It does not execute or test the code itself, meaning runtime errors or integration issues outside the PRD scope are not caught.