umlforge_living_docs
Update existing Mermaid diagrams to reflect sprint or PR changes; produce changelog-annotated diffs, new diagrams, and evolution notes.
Instructions
Update diagrams you already have to reflect what changed in a sprint or PR.
USE THIS WHEN:
You ALREADY HAVE Mermaid diagrams (from a previous generation or your own)
Code has changed in a sprint or PR and your diagrams are now out of date
You want a changelog-annotated diff of your diagrams
NOT FOR:
Generating diagrams for the first time ? use umlforge_reverse_engineer (for existing codebases) or umlforge_stakeholder_arch (for new designs)
Analysing a GitHub URL ? use umlforge_reverse_engineer instead
Generating diagrams without existing ones to update ? use any other tool
IMPORTANT: current_diagrams is REQUIRED ? paste your existing Mermaid diagrams (including the ```mermaid fences). This tool cannot generate from scratch.
Produces:
Updated diagrams for affected sections only (with %% changelog headers)
New diagrams for newly introduced patterns
Architecture evolution note for pasting into a wiki
(report_mode=True) Documentation Analysis Notes: change impact, drift risks, coverage quick wins
Args: current_diagrams: Your existing Mermaid diagram(s) ? paste the full content including ```mermaid fences. REQUIRED. sprint_changes: What changed this sprint: new components, removed flows, renamed services, modified behaviour. affected_files: Files or modules touched in this sprint/PR (optional). report_mode: True ? also produce Documentation Analysis Notes. Pro/Team/Enterprise only.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| report_mode | No | ||
| affected_files | No | ||
| sprint_changes | Yes | ||
| current_diagrams | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |