implement

TDD-driven SDLC implementation translates validated planning artifacts into software by reading project state and user stories, enforcing test-first development, and updating traceability matrices after each feature. It guides developers through feature-by-feature delivery.

Quality gates enforcement blocks commits and pushes unless linting, formatting, type checks, and tests pass. Pre-commit and pre-push git hooks validate code quality automatically before changes are integrated into the project repository.

A traceability matrix links planning artifacts to implemented features. TDD-driven implementation updates the Requirements Traceability Matrix automatically after each feature is completed, ensuring traceability from user stories to delivered software.

Yes, planning artifacts are required. The workflow reads docs/sdlc.state.json, user stories, OpenAPI specs, and ERDs to guide implementation. It validates planning completeness and surfaces guidance when planning artifacts are incomplete.

Yes, artifact-guided implementation reads OpenAPI specs, ERDs, and domain models alongside user stories. These planning artifacts drive the dependency-driven workflow, guiding developers through feature-by-feature delivery and acceptance criteria validation.

The implementation workflow validates planning completeness and surfaces guidance when planning is incomplete. It reads docs/sdlc.state.json and project artifacts, ensuring required user stories and data models exist before starting TDD implementation.