c4-architecture-c4-architecture-v2

name	c4-architecture-c4-architecture-v2
description	C4 Architecture Documentation Workflow workflow skill. Use this skill when the user needs Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
version	0.0.1
category	development
tags	["c4-architecture-c4-architecture-v2","c4-architecture-c4-architecture","generate","comprehensive","architecture","documentation","for","existing"]
complexity	advanced
risk	caution
tools	["codex-cli","claude-code","cursor","gemini-cli","opencode"]
source	community
author	sickn33
date_added	2026-04-19
date_updated	2026-04-25

C4 Architecture Documentation Workflow

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/c4-architecture-c4-architecture from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

C4 Architecture Documentation Workflow Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach. [Extended thinking: This workflow implements a complete C4 architecture documentation process following the C4 model (Context, Container, Component, Code). It uses a bottom-up approach, starting from the deepest code directories and working upward, ensuring every code element is documented before synthesizing into higher-level abstractions. The workflow coordinates four specialized C4 agents (Code, Component, Container, Context) to create a complete architectural documentation set that serves both technical and non-technical stakeholders.]

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Phase 1: Code-Level Documentation (Bottom-Up Analysis), Phase 2: Component-Level Synthesis, Phase 3: Container-Level Synthesis, Phase 4: Context-Level Documentation, Configuration Options, Success Criteria.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Working on c4 architecture documentation workflow tasks or workflows
• Needing guidance, best practices, or checklists for c4 architecture documentation workflow
• The task is unrelated to c4 architecture documentation workflow
• You need a different domain or tool outside this scope
• Use when the request clearly matches the imported source intent: Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

Situation	Start here	Why it matters