From sdlc
BMAD Architecture methodology, quality standards, and reference data for creating architecture decision documents
npx claudepluginhub nexussema/omg-marketplace --plugin sdlcThis skill uses the workspace's default tool permissions.
A BMAD Architecture Document serves two audiences simultaneously:
Guides TDD-style skill creation: pressure scenarios as tests, baseline agent failures, write docs to enforce compliance, verify with RED-GREEN-REFACTOR.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A BMAD Architecture Document serves two audiences simultaneously:
The architecture document ensures all AI agents implement consistently — preventing conflicts in naming, structure, communication patterns, and process decisions.
Every architectural decision must be:
Implementation patterns must be concrete enough that two independent AI agents would produce compatible code:
Project structure must be:
For project classification and starter template guidance:
references/project-types.csv - Project type detection signals and typical startersreferences/domain-complexity.csv - Domain complexity levels and suggested workflows