bmad-agent-architect

Synthesize product requirements into actionable implementation plans within the BMad Method framework.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-agent-architect-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-architect
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-agent-architect
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-agent-architect-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the gap between high-level product requirements and actionable technical architecture, ensuring that system design remains pragmatic, consistent, and aligned with developer productivity.

Core Features & Use Cases

  • Architecture Spine Generation: Defines the invariants and structural rules that keep independently-built units consistent across a project.
  • Implementation Readiness: Validates that PRDs, UX designs, and technical epics are fully aligned before development begins.
  • Use Case: When starting a new feature, use this skill to generate the architecture spine and verify that your technical plan aligns with the project's existing standards and constraints.

Quick Start

Invoke the bmad-agent-architect skill to begin the architecture design process for your current project.

Frequently Asked Questions about bmad-agent-architect

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

FAQPage Schema
How do I translate product requirements into a technical architecture plan?

To translate product requirements into technical architecture, this skill synthesizes PRDs and UX designs into actionable implementation plans, defining the structural rules and invariants that keep your project's independently-built units consistent.

What is an architecture spine and when do I need it for software design?

An architecture spine defines the invariants and structural rules that maintain consistency across independently-built units. You need it when starting new features to ensure the technical plan aligns with existing project standards before development begins.

How do I ensure my technical epics align with my PRD and UX designs?

To ensure technical epics align with PRDs and UX designs, this skill validates implementation readiness by checking that all product requirements, user experience designs, and technical tasks are fully synchronized before development starts.

Do I need project-specific configuration files to use the BMad Method for system design?

Yes, you need access to project-specific customization files and configuration to maintain architectural consistency and persona-driven communication within the BMad Method framework during system design.

What's the best way to define structural rules for consistent system design across a project?

The best way to define structural rules for consistent system design is by generating an architecture spine that establishes invariants across your project, ensuring independently-built units remain aligned with the overarching technical plan.

Why does my technical architecture deviate from the original product requirements?

Technical architecture deviates from product requirements when implementation readiness is not validated first; this skill prevents drift by synthesizing PRDs and UX designs into aligned technical epics within the BMad Method framework.