Skip to content
Skills Library
Programming · Planning

bmad-architect

/bmad-architect

Architecture skill for BMAD. Use for bmad:architecture and bmad:gate-check to produce system design and verify requirement coverage.

Author
xmm ↗
Licence
MIT
Last repository change
19.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
10
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/nfr-checklist.sh, scripts/validate-architecture.sh

What it does and when to use it

Architecture skill for BMAD. Use for bmad:architecture and bmad:gate-check to produce system design and verify requirement coverage.

Original author description

Architecture skill for BMAD. Use for bmad:architecture and bmad:gate-check to produce system design and verify requirement coverage.

How it works

  1. Trigger Intents
  2. Workflow Variants
  3. Inputs
  4. Language Guard (Mandatory)
  5. Mandatory Reference Load
  6. Output Contract
  7. Core Workflow
  8. Gate-Check Criteria
  9. Gate-Check Artifact Format
  10. Script Selection
Original SKILL.md headings · 136 lines, 561 words
SKILL.md preview
---
name: bmad-architect
description: Architecture skill for BMAD. Use for bmad:architecture and bmad:gate-check to produce system design and verify requirement coverage.
---

# BMAD Architect

## Trigger Intents

- `bmad:architecture`
- `bmad:gate-check`

## Workflow Variants

1. `architecture`
- Produce architecture decisions, components, interfaces, and data model.

2. `gate-check`
- Validate architecture quality and requirement coverage before implementation.

Mode selection:
- Run `architecture` when `docs/bmad/architecture.md` does not exist or requirements changed materially.
- Run `gate-check` when architecture exists and the team needs a formal implementation-readiness decision.

## Inputs

- planning artifact (`docs/bmad/prd.md` or `docs/bmad/tech-spec.md`)
- architecture artifact (`docs/bmad/architecture.md`) for gate-check mode
- `bmad/project.yaml` level and constraints
- known integration, compliance, and scalability constraints

## Language Guard (Mandatory)

Enforce language selection separately for chat responses and generated artifacts.

Chat language (`communication_language`) fallback order:

1. `language.communication_language` from `bmad/project.yaml`
2. `English`

Rules for chat responses:

- Use the resolved chat language for all assistant responses (questions, status updates, summaries, and handoff notes).
- Do not switch chat language unless the user explicitly requests a different language in the current thread.

Artifact language (`document_output_language`) fallback order:

1. `language.document_output_language` from `bmad/project.yaml`
2. `English`

Rules for generated artifacts:

- Use the resolved artifact language for all generated BMAD documents and structured artifacts.
- write prose and field values in the resolved document language
- avoid mixed-language requirement clauses with English modal verbs (for example, `System shall` followed by non-English text)
- allow English acronyms/abbreviations in non-English sentences (for example, `API`, `SLA`, `KPI`, `OAuth`, `WCAG`)
- Keep code snippets, CLI commands, file paths, and identifiers in their original technical form.

## Mandatory Reference Load

Before executing `architecture` or `gate-check`, read `REFERENCE.md` first.
Treat `REFERENCE.md` as required context, then load relevant resources and templates.

## Output Contract

- `architecture` -> `docs/bmad/architecture.md`
- `gate-check` -> `docs/bmad/gate-check.md`

## Core Workflow

1. Define system boundaries and architecture drivers.
2. Select architecture pattern and justify trade-offs.
3. Design components, APIs, and data model.
4. Map NFRs to concrete controls and design choices.
5. Run gate-check using criteria from `resources/gate-check-criteria.md` and report pass/fail gaps.

## Gate-Check Criteria

Load and apply `resources/gate-check-criteria.md` as the single source of truth for:
- coverage metric formulas
- blocker classification rules
- `PASS` / `CONDITIONAL PASS` / `FAIL` thresholds

## Gate-Check Artifact Format

Always save `docs/bmad/gate-check.md` using `templates/gate-check.template.md`.

Required sections:
- Executive Summary with decision (`PASS`, `CONDITIONAL PASS`, or `FAIL`)
- Requirements Coverage (FR and NFR totals, coverage percentages, missing items)
- Architecture Quality Assessment (checklist score and failed checks)
- Issues (Blockers, Major Concerns, Minor Issues)
- Recommendations
- Gate Decision (threshold comparison and rationale)
- Next Steps
- Appendix with detailed FR/NFR mapping evidence

## Script Selection

- `architecture` mode:
  ```bash
  bash scripts/nfr-checklist.sh
  bash scripts/validate-architecture.sh docs/bmad/architecture.md
  ```
- `gate-check` mode:
  ```bash
  bash scripts/validate-architecture.sh docs/bmad/architecture.md
  bash scripts/nfr-checklist.sh
  ```

## Template Map

- `templates/architecture.template.md`
- Why: full architecture structure with design decisions and NFR mapping.

- `templates/gate-check.template.md`
- Why: deterministic gate-check report format with objective pass criteria.

## Reference Map

- `REFERENCE.md`
- Must read first for architecture workflow details and design decision quality criteria.

- `resources/architecture-patterns.md`
- Use when selecting monolith, modular monolith, microservices, or other patterns.

- `resources/nfr-mapping.md`
- Use to map performance, security, scalability, and reliability requirements.

- `resources/gate-check-criteria.md`
- Use as mandatory criteria source for gate-check scoring and decision thresholds.

## Quality Gates

- architecture decisions trace back to requirements
- interfaces and data model are explicit
- NFR coverage is documented, not implied
- critical risks and mitigations are listed
- implementation can proceed without unresolved blockers
Files in this package (10)
  • REFERENCE.md 18 KB
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • resources/architecture-patterns.md 23 KB
  • resources/gate-check-criteria.md 2 KB
  • resources/nfr-mapping.md 40 KB
  • scripts/nfr-checklist.sh 6 KB
  • scripts/validate-architecture.sh 8 KB
  • templates/architecture.template.md 21 KB
  • templates/gate-check.template.md 5 KB

Versions

The database has no other skills named bmad-architect.

Database snapshot: 13.11.2026 · package version eeb43b02f52f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bmad-developer
    Implementation skill for BMAD. Use for bmad:dev-story and bmad:code-review to deliver tested code from story specs.
  • 100bmad-ux-designer
    UX design skill for BMAD. Use for bmad:ux-design and bmad:user-flow to define interaction design and accessibility-ready UX artifacts.
  • 90bmad-agent-architect
    System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
  • 90bmad-agent-architect
    System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
  • 90bmad-agent-architect
    System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect
  • 96bmad-update
    Use when updating BMAD or invoking bmad-update.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.