hf-design-review

An evidence-based design review evaluates design drafts against approved specifications to produce a structured verdict. It enforces evidence-driven scoring across architecture, module boundaries, API contracts, data models, and non-functional requirements.

Run a formal design review against approved specifications to assess API contracts and non-functional requirements. The process requires spec traceability, applies evidence-based scoring across six dimensions, and outputs a structured review record with actionable findings.

Yes, a formal design review checks spec traceability by identifying and evaluating module boundaries and data models against approved specifications. It produces a structured verdict with actionable findings to ensure alignment before implementation.

To handle scope drift and evidence conflicts during a design review, use a workflow-aligned approach that provides blocking and reroute paths. This ensures the design remains consistent with approved specifications and produces actionable next-step recommendations.

You need a formal design review for software architecture before implementation to evaluate design drafts against approved specifications. It is required when assessing architecture, API contracts, and non-functional requirements to produce a structured review record.

A design review requires traceability to approved specifications to enforce evidence-based scoring and ensure the design draft aligns with requirements. This process produces a structured verdict with actionable findings and next-step recommendations.