rai-story-implement

Story task implementation using TDD follows a RED, GREEN, REFACTOR cycle for each task, running tests, lint, format, and type checks as verification gates before committing changes to reduce regressions.

Enforcing test-driven development during story plan execution requires applying per-task RED, GREEN, and REFACTOR cycles, running automated verification checks, and committing changes only after local validation passes.

Automating code quality checks and git commits for story tasks involves running configurable manifest-driven commands for tests, lint, formatting, and type checks, then committing individual task changes upon successful verification.

Yes, this TDD workflow tracks story implementation progress by updating progress logs after each task and escalates automatically when repeated test, lint, format, or type check failures occur during the cycle.

Yes, you need a pre-existing story plan file defining sequential tasks, as this workflow executes those tasks individually using TDD and verification gates to produce tested and committed code.

When refactoring fails type checks or lint gates during story implementation, the workflow escalates after repeated failures to prevent inconsistent quality, ensuring changes are fully validated locally before committing.