code-implementation

To turn component specifications into production-ready code, map each spec to a concrete implementation following a structured order: types, entities, repositories, services, and controllers, while building tests in tandem to enforce quality gates.

Enforce coding standards and test coverage by applying quality gates that check specification completeness, linting rules, type safety, and documentation aligned to the technology constraints defined in your project's configuration.

Yes, this specification-to-implementation framework applies across any technology stack by reading tooling requirements from .constraints/TECHNOLOGY.md, ensuring consistent implementation for both greenfield development and project refactors.

Follow the implementation order by first defining types and interfaces, then building entities, repositories, services, and controllers, ensuring tests are implemented alongside each architectural layer.

You need to check .constraints/TECHNOLOGY.md before coding to align your tooling, testing requirements, linting rules, and documentation standards with the specific technology constraints of your project environment.

Yes, the framework supports auditing existing code by verifying specification completeness, test coverage, linting, type safety, and documentation to ensure compliance during refactors or compliance checks.