Skip to content

v3.0.0 - Full port to BMAD v6.2.2

Choose a tag to compare

View all tags
@dexusno dexusno released this 08 Apr 21:33
v3.0.0
9e55364

Full port to BMAD v6.2.2 architecture. Ground-up rewrite. Not backward compatible with v2.x.

Why this release exists

The previous v5-era architecture (XML-style agent files, workflow file triads, manual manifest CSV editing, .claude/commands/ stubs) was incompatible with BMAD v6.2.2's new module system. v3.0 is the result of porting TeamBuilder to be a first-class BMAD v6 custom module installed via BMAD's native --custom-content flow. Every generated team is itself a BMAD v6 custom module.

Highlights

  • 6 agents ported to v6 shape (SKILL.md + bmad-skill-manifest.yaml)
  • 5 skills ported to v6 shape (SKILL.md + workflow.md)
  • 6 pattern libraries rewritten with ~55,000 words of v6-shape examples (31 example agents, 21 example workflows authored by 6 parallel workers)
  • 42+ validation rules rewritten for v6, including the critical code: teams-{name} enforcement
  • Installer rewritten to use BMAD's --custom-content flow — no more manual manifest editing, no more .claude/commands/ stubs
  • teams-{name} module convention for generated teams so bmad-init can resolve them at runtime
  • Comprehensive new README with full documentation and disclaimer

Validation

All gates passed including the Phase 4 smoke test (28/28 PASS) end-to-end round trip: a hand-crafted fake "generated team" was installed as a real BMAD custom module, and both teambuilder and the generated team coexisted cleanly in bmad status.

Install

# Windows
mkdir my-project; cd my-project
iwr https://raw.githubusercontent.com/dexusno/teambuilder/main/scripts/install.ps1 -OutFile install.ps1
.\install.ps1
# Linux/macOS
mkdir my-project && cd my-project
curl -fsSL https://raw.githubusercontent.com/dexusno/teambuilder/main/scripts/install.sh -o install.sh
chmod +x install.sh
./install.sh

Breaking changes

v3.0 is not backward compatible with v2.x. The v5 and v6 architectures are fundamentally different. Existing v2-generated teams must be regenerated with v3 for use on BMAD v6.

See CHANGELOG.md for the complete per-section diff.

Assets 2
Loading