reviewing-technical-design

Hand the finished TDD to this gate, which reads it independently and judges it against 11 implementability conditions covering traceability, decomposition, failure handling, observability, testing, and rollout. It returns a single VERDICT: approve or revise line plus actionable findings.

A ready TDD traces every decision to a requirement bidirectionally, stays scoped to one feature, references rather than duplicates owned contracts, weighs a real alternative, handles each failure mode, names observability signals, covers failure cases in testing, and defines measurable rollback triggers.

Use design-review for generic engineering design docs, RFCs, ADRs, specs, or plans that need claims verified against the codebase. This gate is only for the doc-library technical-design artifact, identified by the template: technical-design frontmatter.

Yes. When handed a change request against an existing TDD, it runs a delta-scoped review of only the changed decisions and their ripple, checking version bumps, changelogs, and SSOT impacts, without re-reviewing the unchanged design.

The bar is proportionate: a small feature legitimately omits migration, concurrency, or a separate observability section. The gate judges completeness of applicable decisions, not section count, and never manufactures gaps from brevity.