blueprint-review

Analyze Blueprint documents for gaps and inconsistencies against ADRs and glossary.

11|Updated Sep 5, 2025

Search Tags:#review #blueprint #drift #acceptance-criteria #stakeholders #gap-analysis #open-questions

Ready to run

npx skills add https://github.com/thrawn01/claude-dotfiles --skill blueprint-review-thrawn01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blueprint-review
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/blueprint-review
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill blueprint-review-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a Blueprint document to identify gaps, ambiguities, inconsistencies, and unresolved questions that would block or drift during build, then produces actionable updates to align product intent with the technical design.

Core Features & Use Cases

Systematically surface gaps in problem scope, acceptance criteria, user stories, and technical constraints.
Flag inconsistencies and open questions, with concrete suggested fixes and updated blueprint excerpts.
Coordinate with ADRs and domain glossary to ensure alignment and traceability across the blueprint lifecycle.

Quick Start

Provide the Blueprint file (and optional CONTEXT/glossary) to generate a structured, ready-to-apply review with recommended updates.

Frequently Asked Questions about blueprint-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find gaps and ambiguities in a product blueprint before development starts?▼

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.

What is blueprint gap analysis and how does it prevent scope drift during build?▼

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.

How do I review acceptance criteria and user stories for technical inconsistencies?▼

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.

Can I align domain glossary terminology and ADRs with my blueprint document?▼

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.

What is the best way to structure blueprint review findings for stakeholders?▼

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.

Do I need a domain glossary to perform a blueprint gap analysis?▼

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.