Offer teams and no-teams variants of commands at install time #58
Description
Problem
The current commands (/implement, /review, /debug, /specify, /resolve) all use Agent Teams. This adds complexity, has the one-team-per-session constraint, and may not be desired by all users. The non-teams implementations (parallel Task() calls) are simpler and still effective.
Proposal
Split command variants into two install options — users choose during `devflow init`:
- With Agent Teams — current implementation using TeamCreate, SendMessage, coordinated teammates
- Without Agent Teams — simpler implementation using parallel Task() spawns, no team lifecycle
Key Constraints
- No runtime flags — this is not `/implement --no-teams`. Users pick a variant at install time and get that version of the commands.
- CLI install choice — `devflow init` presents the option (e.g., as part of the extras multiselect or a dedicated prompt)
- Same command names — both variants use `/implement`, `/review`, etc. — the user just gets whichever version they installed
- Switchable — re-running `devflow init` lets users change their choice
Implementation Ideas
- Two sets of command files per plugin (e.g., `commands/implement.md` vs `commands/implement-teams.md`)
- Init copies the chosen variant as the active command name
- Or: two plugin variants (e.g., `devflow-implement` vs `devflow-implement-teams`)
Motivation
- Agent Teams is experimental and has rough edges (one-team-per-session, idle state complexity)
- Some users may prefer the simpler parallel-task approach
- Keeps the door open for teams to mature without forcing it on everyone