What problem does it solve? Building a Go persistence layer (a repository for one aggregate or a query service for one read contract) requires coordinating tests, implementation, and conventions in the right order. This Skill orchestrates one complete TDD cycle—write failing tests against a real PostgreSQL database, verify red, implement, verify green, then refactor—while delegating the actual test and implementation rules to dedicated convention skills. ## Core Features & Use Cases - Orchestrated TDD cycle: Runs a fixed playbook (fix-unit → write-failing-test → run-red → implement → run-green → refactor → align-errors → report) where the same agent executes each step in declared order. - Dual unit kinds: Handles either one aggregate's Repository interface implementation (standard or event-sourced) or one read contract's query service implementation, dispatching to the matching implementation convention. - Real-database testing: Tests run against actual PostgreSQL via dockertest with pgx/v5, sqlc, and testify, mapping BDD scenarios from data-model documents into table-driven tests with Seed/Read helpers. - Use Case: Given a data-model document with BDD Before/After scenarios for a reservation aggregate, ask the agent to implement its repository via TDD; it writes failing tests first, confirms red, implements the marshaller and sqlc queries, confirms green, and aligns error sentinel translation. ## Quick Start Implement this aggregate's repository with TDD using the BDD scenarios from the attached data-model document, writing the failing tests first.
