System Architect

Design system architectures from product and tech specs.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/coco-de/bmad --skill system-architect-coco-de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: System Architect
Source: https://github.com/coco-de/bmad/tree/main/skills/bmad/bmm/architect
Command: npx skills add https://github.com/coco-de/bmad --skill system-architect-coco-de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System architects struggle to translate requirements into scalable, secure designs that satisfy FRs and NFRs.

Core Features & Use Cases

  • Design system architectures that satisfy functional and non-functional requirements.
  • Define components, interfaces, data models, and API specifications.
  • Document architectural decisions and trade-offs to guide implementation and future changes.

Quick Start

Initiate the architecture workflow from your PRD/tech-spec to generate a complete system blueprint.

Frequently Asked Questions about System Architect

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

FAQPage Schema
How do I design system architecture from functional and non-functional requirements?

To design system architecture from functional and non-functional requirements, translate your PRD or tech-spec into a structured blueprint defining components, interfaces, data models, and API specifications. This ensures your design satisfies both FRs and NFRs for scalable and secure systems.

How do I document architecture decisions and trade-offs for system design?

Documenting architecture decisions and trade-offs involves recording the selected architecture patterns and the rationale behind them within your tech-spec. This documentation guides implementation and future changes by clearly outlining why specific structural choices were made over alternatives.

What is the best way to select architecture patterns for large-scale team projects?

Selecting architecture patterns for large-scale team projects requires evaluating your functional and non-functional requirements. This structured architecture workflow addresses pattern selection by mapping your PRD constraints to scalable component definitions and API specifications suitable for mid- to large-scale teams.

Does this system design workflow work for tech-spec driven projects?

Yes, this system design workflow is applied to Phase 3 workflows specifically for tech-spec driven projects. It enables structured architecture within mid- to large-scale teams by generating a complete system blueprint directly from your initial technical specifications.

When do I need to define API specifications and data models in system architecture?

You need to define API specifications and data models in system architecture when translating requirements into a structured system blueprint. This occurs during the architecture workflow to satisfy functional and non-functional requirements, ensuring component interfaces and data structures are clearly established.