Team
Team is the multi-role path (help menu TE, skill bglad-team). Pair it
with Solo (one person by design). Do not start BMad’s PRD skill
(bmad-prd) for overlay work. The spec lives in the Spec location from
install (Jira, Confluence, or markdown).
flowchart TD
te[Product owner: Problem and Acceptance] --> ds[Tech lead: Design]
ds --> dev[Developer implements]
dev --> askR{Review now or hand off?}
askR --> rv[Required review]
rv --> askQ{Tests now or hand off?}
askQ --> qa[Unit and end-to-end tests]
qa --> mr[Merge request or pull request]
mr --> kn[Knowledge note]
| Who | Skill | Menu |
|---|---|---|
| Product owner (start) | bglad-team | TE |
| Tech lead | bglad-architecture | DS |
| Developer | bglad-dev | DEV |
| Reviewer (or same person) | bglad-review | RV |
| Tester (or same person) | bglad-qa | QA |
| Anyone filing a ticket or change request | bglad-ticket-mr | MR |
| Anyone after the change request | bglad-knowledge | NOTE |
Review and tests are required steps, not extra headcount. After implement the agent asks: run review now, or hand it to someone else? After review passes, the same ask for tests. Prefer another person when one exists. On a small team, the implementer may wear the reviewer and tester hats. Do not skip either step.
One developer doing the whole path by design → Solo.