architecture-docs

Generate evidence-based architecture documentation from repository maps through C4 models and infrastructure diagrams.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/stefaniuk/loadout --skill architecture-docs-stefaniuk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-docs
Source: https://github.com/stefaniuk/loadout/tree/main/.github/skills/architecture-docs
Command: npx skills add https://github.com/stefaniuk/loadout --skill architecture-docs-stefaniuk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to keep architecture documentation accurate and current because manual documentation drifts from the actual codebase. This Skill produces architecture artefacts where every claim is backed by concrete evidence links to code and configuration. ## Core Features & Use Cases - Six-step documentation pipeline: Runs repository mapping, component cataloguing, runtime flow analysis, domain analysis, C4 modelling, and infrastructure diagramming in sequence or individually. - Evidence-first authoring: Every statement cites file paths with line ranges, and anything undeterminable is recorded as "Unknown from code" rather than guessed. - Multiple output formats: Produces Markdown documents, Mermaid diagrams, LikeC4 DSL files, and draw.io infrastructure diagrams with committed SVG exports. - Use Case: Point the Skill at a new FastAPI service repository and run step "all" to generate a complete architecture pack under .copilot/analysis/, from the repository map through to the AWS infrastructure diagram. ## Quick Start Run the architecture-docs skill with step all to generate the full set of architecture artefacts for this repository.

Frequently Asked Questions about architecture-docs

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

FAQPage Schema
How do I generate architecture documentation for an existing repository?▼

Run the architecture-docs skill with step "all" to execute the full six-step pipeline, or specify a single step such as repository-map or c4-model. Outputs are written under .copilot/analysis/ with an index README linking every artefact.

What outputs does the architecture documentation pipeline produce?▼

The pipeline produces a repository map, up to 12 component documents, up to 16 runtime flow documents with Mermaid diagrams, up to 5 domain analysis files, LikeC4 DSL files for C4 context/container/component views, and per-cloud-provider draw.io infrastructure diagrams with SVG exports.

Can I run a single step like the C4 model without running all steps?▼

Yes, individual steps can be run by specifying their slug, such as c4-model or runtime-flows. However, each step depends on outputs from prior steps, so those dependency artefacts must already exist under .copilot/analysis/ before starting.

Does the skill support LikeC4 and draw.io diagram formats?▼

Yes, step 05 authors C4 models in LikeC4 DSL with context, container, and component views, and step 06 creates draw.io diagrams using official AWS, Azure, or GCP icon libraries. Both .drawio source and rendered .drawio.svg files are committed.

What happens when architecture information cannot be found in the code?▼

The skill never guesses or infers unsupported claims. It records "Unknown from code - {suggested action}" for anything that cannot be evidenced, keeping gaps visible for maintainers to resolve.

What are the limitations of evidence-first architecture documentation?▼

The approach only documents what is verifiable in code and configuration, so planned-but-unbuilt components and externally managed resources appear as explicit unknowns. Diagrams must also be re-generated when the underlying IaC or code changes materially.