agent-registry

Organize C4 architecture elements into a centralized registry with YAML frontmatter.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/wtah/spec-master --skill agent-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-registry
Source: https://github.com/wtah/spec-master/tree/main/.claude/skills/agent-registry
Command: npx skills add https://github.com/wtah/spec-master --skill agent-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralized registry to organize and discover architecture elements (systems, containers, components, deployments) with clear responsibilities and interfaces.

Core Features & Use Cases

  • Centralized model of C4 architecture elements.
  • Traceability of responsibilities and required interfaces across system boundaries.
  • Use Case: architects outline system structure and dependencies before design.

Quick Start

Initialize the registry skeleton by creating the .arch-registry directory, adding a system.md, and listing containers, components, and interfaces to define the scope and ownership.

Frequently Asked Questions about agent-registry

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

FAQPage Schema
How do I create a centralized C4 architecture registry for system containers and components?

Initialize a .arch-registry directory, add a system.md file, and list containers, components, and interfaces to define scope and ownership across system boundaries.

What is the best way to map responsibilities and dependencies across C4 system boundaries?

A centralized navigable registry enforces a strict YAML frontmatter schema and path conventions to capture system name, element relationships, and status for downstream agents.

Does the architecture registry require YAML frontmatter for traceability?

Yes, the architecture registry enforces a strict YAML frontmatter schema and path conventions to capture system name, element relationships, and status for downstream agents and traceability.

Can I use this registry to model C4 deployments and interfaces before design?

Yes, architects use the registry to outline system structure and dependencies before design by modeling C4 diagrams across containers, components, deployments, and interfaces.

When do I need a registry for C4 architecture elements?

You need a registry for C4 architecture elements when you want to organize and discover systems, containers, components, and deployments with clear responsibilities and interfaces in a centralized model.