Architecture Documentation

Name: Architecture Documentation
Availability: InStock
Author: Tron

Organize system architecture documentation with Markdown templates and Mermaid diagrams.

Updated Apr 22, 2026

Search Tags:#architecture #documentation #mermaid #adr #runbook #data-flow

Ready to run

npx skills add https://github.com/Trong-Tra/agent-skills --skill architecture-documentation-trong-tra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Documentation
Source: https://github.com/Trong-Tra/agent-skills/tree/main/documentation-specialist/architecture
Command: npx skills add https://github.com/Trong-Tra/agent-skills --skill architecture-documentation-trong-tra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This documentation skill helps teams communicate system structure, data flows, and design decisions to new contributors and operators, reducing onboarding time and confusion.

Core Features & Use Cases

Architecture Overview with system purpose, component list, and data flow
Documentation of Architecture Decisions with ADRs and runbooks
Security boundaries, deployment topology, and maintenance practices

Quick Start

Create Architecture Overview and ADRs starting with a high-level system purpose and a data-flow diagram.

Frequently Asked Questions about Architecture Documentation

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

FAQPage Schema

How do I write architecture documentation for a complex software system with multiple services?▼

Architecture documentation for multiple services should organize system purpose, component relationships, and data flow using Markdown templates and Mermaid diagrams to communicate structure clearly to contributors.

What is the best way to document system data flow and security boundaries?▼

Documenting data flow and security boundaries requires structured Markdown docs with Mermaid diagrams to visualize component relationships, deployment topology, and security perimeters for complex system architectures.

How do I create Architecture Decision Records and runbooks for operators?▼

Architecture Decision Records and runbooks are created using Markdown-based templates to capture design decisions, deployment topologies, and maintenance practices, reducing onboarding time for new operators.

Does this documentation approach work with Mermaid diagrams for deployment topology?▼

Yes, this architecture documentation approach uses Mermaid diagrams to map deployment topology and component relationships, requiring a disciplined approach to visualize complex software systems and data flows.

When do I need to use ADRs in software engineering documentation?▼

Architecture Decision Records are needed when communicating design decisions and system purpose to new contributors, reducing confusion during onboarding for complex software systems with multiple services.