Skip to content

v3.2.2 - Fully automatic team install

Latest
Latest

Choose a tag to compare

View all tags
@dexusno dexusno released this 09 Apr 19:47
v3.2.2
16c02bc

Makes the generated-team install fully automatic — the actual delivery of TeamBuilder's end-to-end automation promise. Backward compatible with v3.0 through v3.2.1.

Why this release exists

v3.2.1 made the install command non-interactive (added the required flags so BMAD's TUI wouldn't block). But it stopped one step short of what TeamBuilder's design actually promises: the generate-team and collaborative-generation workflows still told the user "Here's the install command, run it yourself."

That defeats TeamBuilder's core design point. The user put it exactly right:

"Everything that needs to be installed, must be so automatically. The user must not need to do any manual installing. That's the whole point of teambuilder."

Absolutely right. v3.2.2 closes the gap.

What changed

bmad-skill-generate-team/workflow.md Step 10 — six-sub-step automation protocol

Sub-step What the agent does
10.1 Write the install command into TEAM_README.md as documentation only, marked "for reference — the team was already installed automatically at generation time."
10.2 Resolve absolute {project_root} and {team_path}. Verify both exist. No guessing.
10.3 Announce to the user, then invoke the Bash tool with the complete non-interactive npx bmad-method@6.2.2 install ... command.
10.4 Verify the post-install state: _bmad/teams-{name}/config.yaml exists, agent-manifest.csv has rows, .claude/skills/bmad-agent-{entry-point} landed. Do NOT report success before verification.
10.5 Success report with specific evidence (paths, counts, bmad status confirmation). Tell the user the ONE remaining manual step: restart Claude Code.
10.6 Memory MCP .mcp.json patch is shown, not auto-applied, because .mcp.json may contain credentials.

bmad-skill-collaborative-generation/workflow.md Phase 4 "If INSTALL"

Rewritten to delegate to generate-team Step 10 rather than showing the install command. Removes the duplicated command that could drift out of sync.

README updates

  • Quick Start step 8: "The team installs itself automatically. No copy-paste required."
  • Quick Start step 9: Restart Claude Code (the one remaining user action — a client-side thing no tool can do).
  • "Installing a generated team": Leading paragraph now says TeamBuilder installs automatically. The manual command is preserved below as "if you ever need to reinstall manually."

The new user flow

  1. Discovery (10 questions)
  2. Paired generation (architect + persona-improver)
  3. Quality validation (0–100 score)
  4. User decision: install / refine / regenerate
  5. If install: agent runs npx bmad-method@6.2.2 install ... via Bash tool, verifies the result, reports success. No copy-paste.
  6. Agent: "Restart Claude Code to see your new team."
  7. You restart. Your team is ready.

Zero manual install commands. The only thing the user types is whatever their shell needs to restart Claude Code.

What was NOT changed

  • scripts/install.ps1 / scripts/install.sh — already worked correctly, no changes.
  • scripts/doctor.{ps1,sh} / scripts/update.{ps1,sh} — already correct.
  • TeamBuilder's own agents (other than team-guide reading this workflow).
  • Pattern libraries, validation rules, BMAD compatibility matrix.

Update from any v3.x

# Windows
.\scripts\update.ps1
# Linux/macOS
bash scripts/update.sh

The update script preserves your generated teams under _bmad/teams-*/.

Reported by

The same user who reported the v3.2.1 hang. After v3.2.1 fixed the hang but still told them to copy-paste the command, they pointed out — correctly — that showing the user a manual command to run defeats the whole point of TeamBuilder being an automated team generator. This release is that correction, delivered.

See CHANGELOG.md for the complete diff.

Assets 2
Loading