architecture-documentation

Generate technical architecture documentation with C4 diagrams from codebases.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/dha201/architecture-documentation-plugin --skill architecture-documentation-dha201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-documentation
Source: https://github.com/dha201/architecture-documentation-plugin/tree/main/plugins/architecture-documentation/skills/architecture-documentation
Command: npx skills add https://github.com/dha201/architecture-documentation-plugin --skill architecture-documentation-dha201

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive technical architecture documentation from codebases, saving engineers significant time and ensuring consistency.

Core Features & Use Cases

  • Codebase Analysis: Explores code structure, identifies components, and traces data flow.
  • Diagram Generation: Creates C4 model diagrams (context, container, component) using PlantUML/Kroki or Eraser syntax.
  • Detailed Documentation: Includes component deep dives, decision logs (ADRs), and technology stack summaries.
  • Use Case: A team is onboarding new members to a complex microservices project. This Skill can generate up-to-date documentation, including diagrams and component responsibilities, to accelerate the onboarding process.

Quick Start

Use the architecture-documentation skill to generate architecture documentation for this codebase.

Frequently Asked Questions about architecture-documentation

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

FAQPage Schema
How do I generate architecture documentation from an existing codebase?

Architecture documentation from a codebase is generated by analyzing code structure, tracing data flow, and identifying components to automatically produce detailed system design docs and diagrams.

What is the best way to create C4 model diagrams for a software system?

Creating C4 model diagrams is best handled by automated generation tools that parse your codebase to produce context, container, and component diagrams using PlantUML, Kroki, or Eraser syntax.

Can I automate technical handoff documentation for a microservices project?

Yes, you can automate technical handoff documentation for a microservices project by analyzing the codebase to generate component deep dives, technology stack summaries, and architectural decision logs.

Does this approach work with PlantUML and Kroki for diagram generation?

Yes, this approach works with PlantUML and Kroki for diagram generation, utilizing these rendering engines to visualize C4 model diagrams and component relationships extracted directly from the codebase.

What should be included in a comprehensive architecture review document?

A comprehensive architecture review document should include system diagrams, data flow analysis, component deep dives, technology stack summaries, and architectural decision records to ensure complete technical context.

When do I need automated codebase analysis for system design docs?

You need automated codebase analysis for system design docs when onboarding new team members, performing architecture reviews, or preparing technical handoffs to ensure consistent and up-to-date documentation.