c4-export

Generate Structurizr C4 DSL models from business capability trees.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill c4-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c4-export
Source: https://github.com/papeete-consulting-lab/banking-reliever/tree/main/.claude/skills/c4-export
Command: npx skills add https://github.com/papeete-consulting-lab/banking-reliever --skill c4-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of manually creating and maintaining architecture diagrams by generating consistent Structurizr C4 models from business capabilities, implementation status, and domain information.

Core Features & Use Cases

  • C4 Model Generation: Produces enterprise, zone, and capability-level Structurizr DSL files that represent the product architecture.
  • Architecture Traceability: Links capabilities, DDD elements, implementation artifacts, and ADR references while consuming knowledge through the kpack workflow.
  • Use Case: Help architecture teams visualize where capabilities are implemented, stubbed, or not yet scaffolded across a financial product landscape.

Quick Start

Ask the c4-export skill to regenerate the C4 diagrams for the product capability model and save the Structurizr DSL output under the documentation folder.

Frequently Asked Questions about c4-export

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

FAQPage Schema
How do I generate Structurizr C4 architecture models from business capabilities?

To generate Structurizr C4 architecture models, you can use this Skill to transform business capability trees and implementation metadata into idempotent enterprise, zone, and capability-level DSL files.

What is the best way to visualize where capabilities are implemented or stubbed across a product landscape?

Visualizing implementation status across a product landscape is achieved by generating C4 models that tag capabilities with implementation statuses like implemented, stubbed, or not yet scaffolded.

How does architecture traceability work when linking ADR references to C4 diagrams?

Architecture traceability links capabilities, DDD elements, and implementation artifacts to ADR references by consuming knowledge through the kpack workflow and embedding those links within the Structurizr DSL output.

Can I use kpack-based knowledge retrieval to produce capability mapping diagrams?

Yes, kpack-based knowledge retrieval is required to source the business capability trees and implementation metadata needed to render the capability mapping diagrams via the kproj-c4 rendering workflows.

Do I need to manually maintain Structurizr DSL files if my capability tree changes?

No, manual maintenance is unnecessary because the Skill idempotently regenerates the Structurizr DSL artifacts directly from the updated business capability tree and implementation metadata.

What are the limitations of generating C4 models from business capability trees?

The limitation is that generating these C4 models requires both kpack-based knowledge retrieval and kproj-c4 rendering workflows to be present, as the Skill cannot produce the diagrams without these dependencies.