blueprint-review

To find gaps in a product blueprint, analyze the document for missing problem scope, vague acceptance criteria, and technical inconsistencies. Anchoring findings to ADRs and domain glossaries ensures consistent terminology and produces concrete fixes ready for stakeholder review.

Blueprint gap analysis systematically identifies unresolved open questions and technical constraints that cause scope drift during build. It flags inconsistencies between product intent and technical design, then produces an updated blueprint with actionable fixes to align stakeholders and prevent project drift.

Reviewing acceptance criteria and user stories requires checking them against ADRs and domain glossary entries to surface ambiguities. This process flags inconsistencies and missing technical constraints, generating structured findings with concrete suggested fixes and updated blueprint excerpts for immediate review.

You can align domain glossary terminology and ADRs with your blueprint by providing both documents during the review process. The analysis coordinates these inputs to ensure traceability across the blueprint lifecycle and outputs a structured set of findings with consistent terminology decisions.

The best way to structure blueprint review findings is to produce a categorized set of gaps, inconsistencies, and open questions anchored to ADRs. This structured output includes concrete suggested fixes and an updated blueprint excerpt, making it immediately actionable for stakeholder alignment and build decisions.

A domain glossary is optional but recommended for blueprint gap analysis. Providing the glossary alongside the blueprint allows the review to ensure consistent terminology and traceability across decisions, resulting in more accurate findings and aligned technical constraints for the build phase.