architect-pyramid

Map C4 views, ADRs, and arc42 constraints into a unified artifact pyramid.

86|9|Updated Jun 5, 2026

Search Tags:#architecture #documentation #adr #architect #c4 #arc42 #pyramid

Ready to run

npx skills add https://github.com/magnus919/hermes-profiles --skill architect-pyramid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-pyramid
Source: https://github.com/magnus919/hermes-profiles/tree/main/skills/architecture/architect-pyramid
Command: npx skills add https://github.com/magnus919/hermes-profiles --skill architect-pyramid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Output orchestrator for the technical-architect profile — maps C4 structural views, ADR decision records, and arc42 constraints into a unified artifact pyramid. Manages the pyramid structure, cross-referencing rules, and handoff convention. Load after c4-diagramming, adr-authoring, and arc42-context.

Core Features & Use Cases

Cross-references C4 views to ADRs and arc42 constraints to maintain traceability across architectural layers.
Builds the pyramid structure (summary, analysis, dossiers) and supports deterministic handoffs for agent-driven workflows.
Useful in architecture workstreams requiring reproducible, portable architecture documentation for teams and external reviewers.

Quick Start

Run the architect-pyramid with your project inputs to generate the artifact pyramid from C4 views, ADRs, and arc42 context.

Frequently Asked Questions about architect-pyramid

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

FAQPage Schema

How do I consolidate C4 diagrams, ADRs, and arc42 constraints into a unified architecture document?▼

Consolidating C4 diagrams, ADRs, and arc42 constraints into a unified architecture document is done by mapping them into an artifact pyramid. This enforces cross-referencing rules and produces a portable, human- and machine-readable structure.

What is an artifact pyramid in software architecture?▼

An artifact pyramid is a unified structure that maps and consolidates architectural artifacts like C4 views, ADR decision records, and arc42 constraints. It organizes these elements into summary, analysis, and dossier layers for reproducible documentation.

How do I maintain traceability across C4 container diagrams and architecture decision records?▼

Traceability across C4 container diagrams and architecture decision records is maintained by enforcing cross-referencing rules within an artifact pyramid. This links system context, container and component diagrams directly to relevant decision logs.

Can I use this approach to generate portable architecture documentation for external reviewers?▼

Yes, this approach generates portable architecture documentation suitable for external reviewers. By consolidating C4 views and arc42 constraints into a pyramid, it produces a reproducible format that both teams and external stakeholders can read.

Do I need existing arc42 context and C4 views before building an architecture artifact pyramid?▼

Yes, you need existing arc42 context and C4 views before building an architecture artifact pyramid. The process maps these pre-existing structural views and decision records into the unified pyramid structure.

How does the artifact pyramid support agent-driven architecture workflows?▼

The artifact pyramid supports agent-driven architecture workflows by defining a deterministic pyramid structure and handoff convention. This allows automated agents to reliably process and transfer the consolidated architectural artifacts.