Problem
BMAD 6.2.2 agents run bmad_init.py check before activation to verify the project has been configured. With global sideshow installation, there is no per-repo _bmad/ with module configs, so the check fails:
{"init_required": true, "missing_module": "bmm"}
{"init_required": true, "missing_module": "core"}
The agent then tries to run bmad_init.py check --module bmm which also fails because it expects per-project BMAD config files.
Context
This is new in BMAD 6.2.2 — the init scripts are Python (core/bmad-init/scripts/bmad_init.py). They verify project-level configuration before allowing agent activation. This worked when _bmad/ was per-repo.
Options
- sideshow init — creates minimum per-repo config shim that satisfies the init check
- Patch scripts during sync — wrap bmad_init.py so it checks global path
- Replace init gate — sideshow's own init that understands global layout
- Skip the gate — modify the agent commands to skip the init check when running from global installation
Evidence
Screenshots from probe test: /bmad-agent-bmm-pm in aclaude (no local _bmad/) triggered init failures.
Problem
BMAD 6.2.2 agents run
bmad_init.py checkbefore activation to verify the project has been configured. With global sideshow installation, there is no per-repo_bmad/with module configs, so the check fails:The agent then tries to run
bmad_init.py check --module bmmwhich also fails because it expects per-project BMAD config files.Context
This is new in BMAD 6.2.2 — the init scripts are Python (core/bmad-init/scripts/bmad_init.py). They verify project-level configuration before allowing agent activation. This worked when _bmad/ was per-repo.
Options
Evidence
Screenshots from probe test:
/bmad-agent-bmm-pmin aclaude (no local _bmad/) triggered init failures.