System Architect

Name: System Architect
Availability: InStock
Author: kmshihab7878

Design system architectures mapping FRs/NFRs to components and patterns.

6|1|Updated Apr 7, 2026

Search Tags:#design #architecture #documentation #system-architecture #prd #nfr #fr

Ready to run

npx skills add https://github.com/kmshihab7878/claude-code-setup --skill system-architect-kmshihab7878

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: System Architect
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/bmad/bmm/architect
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill system-architect-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often struggle to translate requirements into robust, scalable architectures. This skill provides structured system architecture design, decision rationales, and clear patterns to satisfy FRs and NFRs from PRDs.

Core Features & Use Cases

Phase 3 architecture design and documentation that maps FRs/NFRs to components, interfaces, and patterns.
Evaluate trade-offs and select appropriate architectural patterns (e.g., Modular Monolith, Microservices) with justification.
Produce artifacts (architecture diagrams, decision logs, API specs) and load into the project workflow for implementation.
Use Case: When starting a new product or feature requiring reliable scale and maintainability, generate an architecture blueprint.

Quick Start

Provide the PRD or tech-spec and run the architecture workflow to generate a complete system design.

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?▼

Design system architecture by mapping functional and non-functional requirements to components, interfaces, and patterns. This approach translates PRD or tech-spec inputs into structured architecture blueprints, capturing decision rationales and trade-offs for reliable scale and maintainability.

What is the best way to document architecture decisions and trade-offs for microservices?▼

Document architecture decisions and trade-offs by generating decision logs, architecture diagrams, and API specs. This ensures that pattern selections, such as microservices or modular monoliths, are captured and traceable within your project workflow.

How do I choose between a modular monolith and microservices for my system architecture?▼

Choose between a modular monolith and microservices by evaluating trade-offs against your specific FRs and NFRs. This process selects appropriate architectural patterns with justification, ensuring the chosen structure satisfies your project's scale and maintainability requirements.

Do I need a PRD to generate a complete system architecture blueprint?▼

Yes, you need a PRD or tech-spec to generate a complete system architecture blueprint. Providing these requirement documents as input allows the architecture workflow to map functional and non-functional needs to robust system designs and documentation.

What architectural artifacts should I produce for a new product requiring reliable scale?▼

Produce architectural artifacts like architecture diagrams, decision logs, and API specs for new products requiring reliable scale. These outputs map FRs and NFRs to concrete components and integration points, loading directly into the project workflow for implementation.

micaelmalta

architect

Draft technical specifications covering architecture, APIs, data models, and migrations.

Community

Advanced

bwgz

design-documentation

Translates approved requirements into comprehensive technical designs with architecture diagrams, component interfaces, data models, and decision logs.

Community

Intermediate