What is Architecture Design?

A structured approach to define system architecture, choose technology stacks with justification, and document Architecture Decision Records (ADRs).

What inputs are required?

Project name, product requirements document (prd), complexity level, and optional uxDesign artifacts.

What outputs are produced?

An architectural artifact bundle including component diagrams, tech stack rationale, data models, API contracts, ADRs, and a readiness assessment.

Architecture Design

Scanned

npx machina-cli add skill a5c-ai/babysitter/architecture-design --openclaw

Files (1)

SKILL.md

896 B

Architecture Design

Design comprehensive system architecture with technology selection and ADRs.

Agent

Winston (Architect) - bmad-architect-winston

Workflow

Define high-level system architecture with components
Select technology stack with justification
Design data model and database architecture
Define API contracts and integration patterns
Plan security, scalability, and deployment
Document Architecture Decision Records (ADRs)
Validate implementation readiness

Inputs

projectName - Project name
prd - Product Requirements Document
uxDesign - UX design artifacts (optional)
complexity - Project complexity level

Outputs

System architecture with component diagram
Technology stack with rationale
Data model and API contracts
ADRs and readiness assessment

Process Files

bmad-orchestrator.js - Phase 3 of full lifecycle

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/bmad-method/skills/architecture-design/SKILL.md

View on GitHub

Overview

Architecture Design creates a complete system blueprint, selecting technologies with rationale and documenting ADRs. It delivers artifacts such as a component diagram, data model, API contracts, and readiness assessment to guide implementation.

How This Skill Works

It ingests inputs like projectName, prd, uxDesign, and complexity, then defines a high-level architecture with components. It selects a technology stack with justification, designs the data model and API contracts, and outlines security, scalability, and deployment plans. Finally, it records Architecture Decision Records (ADRs) and produces readiness assessments and the required artifacts.

When to Use It

Kick off a new project needing a full architecture and ADRs
Re-evaluate technology stack or select a justification for a solution
Design data model and database architecture to support requirements
Define and standardize API contracts and integration patterns
Plan security, scalability, and deployment while capturing ADRs

Quick Start

Step 1: Gather inputs (projectName, prd, complexity; collect uxDesign if available) and define scope.
Step 2: Draft high-level architecture and component diagram; outline data model and API contracts.
Step 3: Select tech stack with justification, write ADRs, and prepare readiness assessment.

Best Practices

Start with a clear scope and constraints, including inputs and required deliverables
Build a component diagram and data model before selecting tech stack
Justify technology choices with trade-offs and non-functional requirements
Capture decisions in ADRs with rationale, alternatives, and timestamps
Validate readiness with architectural reviews and incremental milestones

Example Use Cases

Architecture for a multi-service e-commerce platform with ADRs
Data-intensive analytics pipeline with data modeling and API contracts
Mobile backend architecture with authentication, rate limiting, and caching
IoT device ingestion gateway with scalable streaming and data models
SaaS platform with multi-tenant architecture and deployment plan

Frequently Asked Questions

Add this skill to your agents