bmad-agent-architect

Guide distributed system design decisions using the BMAD framework and NONoise adaptations.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill bmad-agent-architect-russosalv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-architect
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/bmad-agent-architect
Command: npx skills add https://github.com/russosalv/NONoise --skill bmad-agent-architect-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alex provides a System Architect persona to guide users through technical design decisions, distributed systems planning, and architectural validation, helping teams articulate robust, scalable designs.

Core Features & Use Cases

  • Architecture brainstorming and option exploration using canonical patterns and trade-off analysis.
  • Formal validation of PRDs using Quint FPF, and generation of ADRs to capture decisions and rationales.
  • Documentation alignment and handoff to source-of-truth docs (architecture/ and PRD alignment) with LSP advice.
  • On-activation context loading from project context to tailor guidance and handoffs to the current tech stack.

Quick Start

Ask Alex to outline a scalable architectural design for a distributed system.

Frequently Asked Questions about bmad-agent-architect

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

FAQPage Schema
How do I design a scalable architecture for a distributed system?

To design a scalable distributed system architecture, this persona guides you through technical design decisions using canonical patterns and trade-off analysis. It loads project context to tailor architectural brainstorming and option exploration specifically to your tech stack.

What is the best way to validate PRDs for technical projects?

Validating PRDs is best handled through formal validation using the Quint FPF framework. This process ensures technical readiness by checking alignment against distributed systems design requirements and generating ADRs to capture decisions and rationales.

Can I generate Architecture Decision Records for distributed systems planning?

Yes, you can generate Architecture Decision Records (ADRs) during distributed systems planning. The system architect persona captures technical decisions and rationales formally, ensuring documentation alignment and providing a clear handoff to source-of-truth docs.

Does this approach work with existing architecture documentation?

Yes, it integrates directly with existing architecture documentation. The system loads on-activation context from your project to align guidance, tailoring architectural handoffs and providing LSP advice to maintain consistency with source-of-truth docs.

When do I need an LSP advisor for system design?

You need an LSP advisor for system design when aligning technical documentation and preparing for implementation readiness. It surfaces canonical architectures with inline recommendations, ensuring smooth handoffs across discovery and implementation phases.