export-diagrams

Generate Mermaid architecture diagrams from code and plan-doc deltas, optionally Structurizr DSL via --engine flag, into docs/diagrams/

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-diagrams-tacuchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-diagrams
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/exports/export-diagrams
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill export-diagrams-tacuchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workspace architecture evolves as code and plans change; this skill automates creating a coherent set of architecture diagrams from sources and plan-doc deltas to keep everyone aligned.

Core Features & Use Cases

  • Generate context, container, component, and integration diagrams from code and plan-doc deltas.
  • Default to Mermaid diagrams with optional Structurizr DSL via the --engine flag; output is written under docs/diagrams/NNN-export-diagrams-YYYY-MM-DD/.
  • Read-only artefact generation: no code mutation, no commits, suitable for audits and onboarding.

Quick Start

Invoke the CLI with aw export-diagrams to generate the diagrams dossier under docs/diagrams using the default mermaid engine.

Frequently Asked Questions about export-diagrams

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

FAQPage Schema
How do I automatically generate architecture diagrams from code and plan-doc deltas?

Generate architecture diagrams by reading source code and plan-doc deltas to produce Mermaid context, container, component, and integration diagrams by default, writing the output dossier under docs/diagrams/.

What types of architecture diagrams can I create from my workspace?

You can create context, container, component, and integration diagrams from your workspace sources and plan-doc deltas. The skill tracks AS-IS and TO-BE states across sessions to keep everyone aligned on evolving architecture.

Can I export Structurizr DSL instead of Mermaid diagrams?

Yes, export Structurizr DSL instead of Mermaid by invoking the CLI with the --engine flag to customize the output engine. Mermaid remains the default diagram format for generated architecture dossiers.

Does generating workspace diagrams modify my source code or create git commits?

No, generating workspace diagrams is a read-only artefact generation process that respects read-only constraints. It performs no code mutation and creates no commits, making it suitable for audits and onboarding.

What's the best way to track AS-IS and TO-BE architecture states across development sessions?

Track AS-IS and TO-BE architecture states by exporting diagrams from code and plan-doc deltas across sessions. The skill applies to software development workflows that monitor evolving workspace architecture and writes dossiers under docs/diagrams/.