What problem does it solve? Turning architecture documents (OpenAPI specs, ERDs, ADRs) into working backend code is slow and error-prone, often producing inconsistent patterns across services. This Skill reads the Solution Architect's outputs and generates complete service implementations with handlers, business logic, repositories, middleware, tests, and local dev tooling. ## Core Features & Use Cases - Contract-Driven Implementation: Reads OpenAPI, gRPC, AsyncAPI specs, ERDs, and ADRs, then implements services faithfully without redesigning the architecture. - Clean Architecture Generation: Produces thin handlers, pure service-layer business logic, tenant-scoped repositories, and dependency injection wiring per service. - Cross-Cutting Infrastructure: Builds auth middleware (JWT/JWKS), tenant resolution, structured logging, rate limiting, caching, circuit breakers, feature flags, and graceful degradation. - Parallel Multi-Service Builds: Establishes shared foundations in libs/shared first, then dispatches one agent per service for consistent parallel implementation. - Use Case: Given an architecture defining user-service, payment-service, and notification-service, generate all three services with tests, docker-compose dev stack, seed data, migrations, and a root Makefile. ## Quick Start Ask the agent to implement the backend services defined in the api/ and docs/architecture/ directories of your project.
