Technical Design Quality Review

Review a technical design before implementation for boundaries, dependencies, failure modes, data consistency, security, performance, observability, compatibility, maintainability, and verification readiness. It produces TD-## findings and validation preparation; it does not review unsupplied code or approve architecture.

When to Use

• Use it for ADRs, component/data-flow designs, technical proposals, and non-functional constraints.
• Use it to identify failure paths, dependency assumptions, compatibility risks, and evidence gaps.
• Use it when an incomplete design still needs a bounded implementation-readiness pass.

Do not use it to run builds, tests, production probes, or choose a final architecture for a Human.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use