spec-diagram-review

Detect semantic inconsistencies across specification diagrams and acceptance criteria.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill spec-diagram-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-diagram-review
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/spec-diagram-review
Command: npx skills add https://github.com/friedbotstudio/baseline --skill spec-diagram-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches semantic drift in drafted specifications by checking that diagrams, schemas, and acceptance criteria all tell the same story before approval.

Core Features & Use Cases

  • Cross-diagram consistency review: Verifies that C4 container and component structures align with the dependency graph.
  • Schema change validation: Checks that class diagram field changes are mirrored by matching migration DDL.
  • Behavior traceability: Confirms that every acceptance criterion points to a real sequence and that every sequence is referenced.
  • Use Case: Use it after a spec passes linting to find architectural mismatches, missing migrations, or ungrounded behaviors without modifying files.

Quick Start

Review docs/specs/<slug>.md for diagram consistency and report every semantic mismatch with precise section pointers.

Frequently Asked Questions about spec-diagram-review

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

FAQPage Schema
How do I check for semantic drift between C4 diagrams and acceptance criteria in a specification?

To check for semantic drift, review the specification to ensure C4 container structures, dependency graphs, and sequence interactions align with the acceptance criteria. This cross-diagram consistency review identifies architectural mismatches before approval.

How do I validate that class diagram field changes have matching migration DDL?

Validate schema changes by cross-checking the class diagram field modifications against the migration DDL. This ensures every data structure alteration is properly mirrored by a corresponding database schema migration within the specification.

What is the best way to trace acceptance criteria to sequence diagrams before spec approval?

Tracing acceptance criteria involves confirming every criterion points to a real sequence interaction and that every sequence is referenced. This behavior traceability check grounds the requirements in actual system flows.

Can I review drafted specs for container boundary and dependency node alignment without modifying files?

Yes, you can review drafted specs without modifying files. The process cross-checks container boundaries and dependency nodes while reporting semantic inconsistencies with precise section pointers directly in the output.

When do I need to run a specification diagram consistency review?

You need a diagram consistency review after a specification passes linting but before approval. It detects architectural mismatches, missing migrations, and ungrounded behaviors across C4 views, class diagrams, and acceptance criteria.

Why does my dependency graph show nodes that are missing from the C4 component view?

A dependency graph may show missing C4 component nodes due to semantic inconsistencies in the drafted specification. Cross-checking container boundaries and dependency nodes reports these architectural mismatches with precise section pointers.