What problem does it solve? It removes ambiguity about how to build a Go handler layer RPC with test-driven development by enforcing a fixed cycle: write the API test first, confirm it fails for the right reason, implement the minimal server code, confirm green, then align with language, error, and logging conventions. ## Core Features & Use Cases - TDD cycle orchestration: Runs one RPC as a single unit through fix-unit, write-failing-test, run-red, implement, run-green, refactor, align-errors, align-logs, and report steps defined in playbook.yml. - Convention delegation: Delegates test shape to the handler test convention, implementation form to the handler implementation convention, and error/log alignment to their respective conventions without redefining them. - Stop and resume conditions: Classifies red-test failure reasons, refuses to proceed on unrelated failures, and reports completed steps and open decisions when stopped. - Use Case: Given a proto service with a ConfirmReservation RPC and a finished usecase, ask the agent to implement that RPC via TDD; it writes the API test against a production-equivalent server assembly, watches it fail, implements the server method and conversion functions, and refactors to conventions. ## Quick Start Ask the agent to implement this RPC with TDD, writing the API test first and confirming red before implementing the handler.
