verify-proposed-diag

Verify architecture diagrams against actual codebase and report mismatches.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Trecek/useful-claude-skills --skill verify-proposed-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-proposed-diag
Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/verify-proposed-diag
Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill verify-proposed-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify a proposed architecture diagram's factual accuracy against the actual codebase, recognizing that diagrams may mix existing components (fully verifiable), modified components (partially verifiable), and new components (only integration points verifiable).

Core Features & Use Cases

  • Mermaid syntax validation to ensure renderability of diagrams.
  • Selective verification that respects ★ and ● annotations and focuses on existing interfaces.
  • End-to-end traceability of connections between components to surface mismatches after planning diagrams.

Quick Start

Provide the proposed architecture diagram and the actual codebase, then verify matches and report any discrepancies.

Frequently Asked Questions about verify-proposed-diag

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

FAQPage Schema
How do I verify a proposed architecture diagram against my actual codebase?

To verify a proposed architecture diagram against your codebase, provide both the diagram and code to validate existing interfaces, check component connections, and report mismatches with actionable findings.

What is the best way to validate mermaid syntax for architecture diagrams?

Validating mermaid syntax involves checking the proposed architecture diagram's renderability, ensuring mermaid blocks render correctly while verifying that component connections match real codebase interfaces.

Can I check new and modified components marked with annotations during codebase validation?

Yes, codebase validation respects ★ and ● annotations, selectively verifying existing interfaces and focusing on partially verifiable modified components and new component integration points.

Why does my proposed architecture diagram show mismatched component connections after planning?

Mismatched component connections occur when proposed architecture diagrams lack end-to-end traceability against real interfaces; verifying diagrams surfaces these mismatches with actionable findings.

Do I need to provide the actual codebase to verify diagram accuracy?

Yes, you need to provide the actual codebase to verify a proposed architecture diagram's factual accuracy, allowing selective verification of existing interfaces and component connections.