Overview

Knowledge Graph Management captures architectural patterns and design decisions in the knowledge graph. It validates graph consistency, enables pattern queries, and syncs the graph with the codebase to reflect reality. Exports to DOT for easy visualization.

How This Skill Works

The skill uses the Maestro toolkit (Read, Write, Edit, Bash, Grep, Glob) to load and update the .maestro/knowledge.dot. It validates consistency, supports targeted updates via Edit, and syncs the graph with codebase reality, with DOT export handled via Bash for visualization.

When to Use It

• After capturing a new architectural pattern or design decision
• When the codebase reality diverges from the knowledge graph
• Before feature releases to verify pattern selections
• During post-merge updates or hotfix retrospectives
• During maintenance to keep the knowledge graph in sync with code changes

Quick Start

1. Step 1: Use Read to load the .maestro/knowledge.dot
2. Step 2: Use Edit to update patterns and decisions, then Write
3. Step 3: Use Bash to export a DOT visualization

Best Practices

• Keep knowledge.dot modular by pattern family and scope
• Validate graph consistency after each Edit with checks or tests
• Link graph references with code using Grep/Glob searches
• Export DOT regularly to share visualizations with the team
• Document changes with descriptive commits and timestamps

Example Use Cases

• Capture a microservices interaction pattern and reference it across services
• Validate architecture decisions across modules to ensure consistency
• Sync the graph after a major merge to reflect new patterns
• Export DOT to share the current architecture with stakeholders
• Record postmortems to capture lessons learned and updated patterns

Frequently Asked Questions