devbooks-coder

Automate test-driven delivery by enforcing tasks.md adherence and gate-based verification to validate implementations. This workflow forbids test modifications and requires verifiable evidence through tests, static checks, and builds to ensure auditable traceability.

Gate-based verification is a mechanism that enforces Knife-style slicing to block progression on failures. It validates progress through tests, static checks, and builds, ensuring auditable outcomes and preventing silent approvals during the implementation workflow.

Generate auditable evidence by running tests and static checks to produce green evidence after implementing tasks.md items. The workflow saves this evidence to the change package and uses gate-based validation for structured progress tracking.

No, you cannot modify tests to force a green build during the implementation workflow. The protocol explicitly forbids test modifications, requiring verifiable evidence through original tests, static checks, and builds to ensure strict separation of duties.

Track real-time progress by maintaining per-task status within the workflow, which prevents silent approvals. The system provides structured outputs for progress and evidence, routing failures to CI gates to block further progression until resolved.