diagram-maintenance

What problem does it solve?

Stale, inconsistent, or missing architecture diagrams and unclear project progress tracking create misalignment between engineering teams and codebases, wasting hours of manual reconciliation and leading to outdated documentation that does not reflect actual system state.

Core Features & Use Cases

• Diagram Auditing: Scan all architecture diagrams for traceability gaps, stale references to deleted source files, missing index entries, and outdated existence/state claims (e.g., "not yet built" labels for already deployed features).
• Diagram Maintenance: Update existing diagrams to reflect code changes, create new diagrams for undocumented components or workflows, and regenerate outdated SVG outputs from PlantUML source files.
• Plan Status Visualization: Generate HTML artifacts that show the current progress of phased project plans, with status aligned to actual git commit history to avoid discrepancies between planning documents and delivered work.
• Use Case: For a team with 20+ architecture diagrams across multiple services, use this skill to quickly identify which SVGs are out of sync with their PUML sources and which diagrams have outdated labels for features that have already been shipped.

Quick Start

Use the diagram-maintenance skill to audit all architecture diagrams for stale traceability notes and out-of-sync SVG files.