What problem does it solve? Turning architecture documents (OpenAPI specs, ERDs, ADRs) into working, consistent backend code is slow and error-prone. This Skill reads the Solution Architect's outputs and generates production-grade service implementations — handlers, services, repositories, middleware, tests, and local dev tooling — without redesigning the agreed architecture. ## Core Features & Use Cases - Contract-driven implementation: Reads api/openapi/*.yaml, schemas/erd.md, migrations, and ADRs, then implements every endpoint faithfully with clean architecture layers (handlers → services → repositories). - Parallel multi-service builds: Establishes shared foundations (libs/shared/ types, errors, auth middleware) first, then fans out up to 3 concurrent sub-tasks to implement services in parallel. - Built-in cross-cutting concerns: Generates auth/tenant middleware, RFC 9457 error handling, structured logging with PII redaction, rate limiting, caching, circuit breakers, OpenFeature feature flags, and OpenTelemetry telemetry. - Use Case: After the architect defines a SaaS API with three services, run this Skill to produce compilable services with tests, docker-compose dev stack, seed data, Makefile gates (make arch, make security-scan, make smoke-telemetry), and a one-command local setup. ## Quick Start Ask the drydock orchestrator to implement the backend services defined in the api/ and schemas/ architecture contracts, or invoke the software-engineer skill directly on a project containing those specs.
