c4doc

C4 Architecture Documentation Skill

Command: /c4doc

Use this skill when the user calls /c4doc or asks to generate or refresh C4 architecture documentation for the current repository.

Purpose

Use this skill to generate or refresh practical C4-style architecture documentation for a software repository.

The generated documentation must be stored in Markdown files and must use standard Mermaid diagrams that render in GitHub Markdown. Do not use Mermaid C4 syntax. Use ordinary flowchart diagrams for static architecture views and sequenceDiagram only for dynamic runtime flows.

The goal is not to force every repository into every C4 level. The goal is to create the minimum useful architecture documentation set for the repository, with clear diagrams, evidence, assumptions, and review notes.

Slash Command

Use this skill when the user calls:

/c4doc

The skill should inspect the current repository, create or refresh repository-specific C4 architecture documentation, and treat any additional user text as scoping guidance for which systems, views, or areas need attention.

Primary Output Location

Create or update files under the repository being documented:

docs/c4-documentation/

Recommended structure:

docs/c4-documentation/
  index.md
  architecture-model.md
  generation-report.md
  system-context.md
  container.md
  components/
    <container-name>.md
  code/
    <component-name>.md
  deployment/
    <environment-or-platform>.md
  dynamic/
    <use-case>.md

Use stable, lowercase, hyphenated filenames.

Lightweight Provenance Block

Every generated Markdown document must include a small provenance block near the top, directly after the title and before status fields, summary tables, or document metadata.

This applies to generated C4 indexes, architecture models, generation reports, system context views, container views, component views, code views, deployment views, and dynamic views created or updated by this skill.