implementation

Coordinating architecture decisions with TDD loops requires an ID-driven workflow that defines domain boundaries, records ADRs, and generates test stubs before iterating on code until all tests pass.

An ID-driven workflow for test-driven development processes one feature @id at a time, generating test stubs, updating signatures, and validating green tests to enforce strict TDD loop discipline.

To generate test stubs and ADRs, first verify prerequisites by reading discovery docs and package metadata, then scaffold architecture-first domain stubs and record ADRs before writing tests.

Yes, discovery documentation is required before starting architecture-first TDD; the workflow enforces reading discovery docs, features, and validating package structure to ensure project readiness.

Quality gates enforced during TDD loop iteration include mandatory review, lint, and test-coverage milestones that must pass before advancing the feature toward handoff and green integration.

You should avoid a single-feature ID-driven TDD workflow when project prerequisites are missing, package structure is invalid, or discovery documentation is incomplete, as the workflow enforces readiness checks.