deployment-architecture

Map containers and components to infrastructure targets with C4 deployment diagrams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formalizes deployment architecture by mapping containers and components to infrastructure targets, enabling consistent, implementable specs from a single source of truth.

Core Features & Use Cases

  • Container-to-Infrastructure Mapping: Link every container and its components to concrete infrastructure services (compute, storage, network, and data stores).
  • C4 Deployment Diagrams: Produce and maintain environment-specific deployment diagrams that reflect current architecture.
  • DevOps-Ready Outputs: Generate environment-ready specifications and runbooks that DevOps teams can implement with IaC tools.

Quick Start

Map the core containers to infrastructure targets and generate an overview and deployment plan.

Frequently Asked Questions about deployment-architecture

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

FAQPage Schema
How do I map containers to infrastructure targets for deployment?

You can generate C4 deployment diagrams by mapping containers and components to infrastructure targets across development, staging, and production environments. This provides environment-specific visual architectures that reflect your current deployment setup.

Can I use this for brownfield deployment architecture or is it only for greenfield projects?

This deployment architecture approach applies to both brownfield and greenfield projects. It formalizes your infrastructure mapping by producing environment-specific C4 diagrams and IaC-ready outputs regardless of your project's current lifecycle stage.

How do I generate IaC-ready deployment specifications from container maps?

You generate IaC-ready outputs by providing explicit container-to-infrastructure mappings and environment blueprints. This produces DevOps-ready specifications with defined service types, sizes, and configurations that teams can implement directly with infrastructure as code tools.

Do I need to define environment blueprints for dev, staging, and production separately?

Yes, you need environment blueprints for development, staging, and production. The architecture mapping requires explicit container-to-infrastructure definitions for each environment to produce accurate C4 deployment diagrams and architecture-registry inputs.

What is the best way to maintain deployment diagrams as infrastructure changes?

The best way to maintain deployment diagrams is using a single source of truth that formalizes container-to-infrastructure mapping. This enables consistent, implementable specs and produces environment-specific C4 deployment diagrams that reflect your current architecture.