CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-architecture

Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a ticket file, with an existing codebase or architecture document beside it. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written orchestration skill: explicit command lines, a sequenced create/update/validate flow with a real reviewer gate and feedback loops, and clean offloading of mechanics to two one-level-deep reference files. The only residual cost is repetition of the coaching-default rule and some extreme sentence density that a light trim would fix.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence ('Record decisions, not rationale (rationale lives in the memlog)', 'Carry shape in diagrams, not prose') with no padding about known concepts, but the Coaching-path default is stated three times (Overview area, 'How you work', Activation step 5) and the Reviewer Gate is pointed at four times, so a trim pass would earn the top anchor.

4 / 5

Actionability

Concrete executable commands appear where they matter ('uv run {project-root}/_bmad/scripts/memlog.py init --workspace {doc_workspace} --field scope="…"', 'npx skills add bmad-code-org/BMAD-METHOD --skill bmad', 'resolve_config.py --key core.output_folder --key core.active_initiative') plus a concrete output path convention ('architecture-{slug}/architecture-{slug}.md'); minor gaps remain where guidance depends on config values like {workflow.spine_template} that are never exemplified.

4 / 5

Workflow Clarity

Activation steps 1-6 and Finalize steps 1-8 are explicitly sequenced with validation checkpoints (deterministic lint pass, then reviewer subagents, fixes resolved 'before polish', triage of open questions and [ASSUMPTION] tags) and explicit error-recovery loops (script-not-found → offer BMad setup → rerun; existing run folder → offer resume from memlog; no active_initiative → hand off then rerun).

5 / 5

Progressive Disclosure

The body is a clear working overview with well-signaled one-level-deep references — 'full mechanics in references/reviewer-gate.md', 'follow references/headless.md for the whole run' — and both files exist, contain the promised detail, and reference nothing deeper; the template and lint script are correctly split into assets/ and scripts/.

5 / 5

Total

18

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit what-and-when structure, and natural quoted trigger phrases that clearly demarcate the skill. Keyword coverage and distinctiveness are good rather than exhaustive, leaving small room for synonyms.

DimensionReasoningScore

Specificity

It names the domain and several concrete actions — 'Creates, updates, or validates one; works from a ticket file, with an existing codebase or architecture document beside it' — matching 'several specific actions; minor gaps'; it is not a 5 because the opening framing ('keep separately built parts of a system consistent') is conceptual rather than an additional concrete capability.

4 / 5

Completeness

It explicitly answers both questions: what ('Work out and record the architecture decisions… in a short architecture document') and when ('Use when the user says "create the architecture", …'), matching the anchor-5 pattern of concrete capabilities followed by explicit trigger phrases.

5 / 5

Trigger Term Quality

The quoted triggers ('create the architecture', 'create technical architecture', 'architecture spine', 'create a solution design') are phrases a user would naturally say, giving good coverage; it falls short of comprehensive because natural variants like 'design the system', 'technical design doc', or 'architecture document' are absent.

4 / 5

Distinctiveness Conflict Risk

Distinctive triggers like 'architecture spine' carve a clear niche with minimal conflict, but 'create a solution design' overlaps slightly with adjacent design-document skills, so it sits at 'mostly distinct; minor overlap risk' rather than the top anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-architecture/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.