Problem
When a user runs a paused squad, they see this error:
✗ Squad "outreach" is paused (since 2026-06-12)
Reason: founder freeze
Use --force to run anyway, or resume with: squads resume outreach
They are directed to use --force. If they check squads run --help, they see:
--force Force re-run squads that already completed today
The description only mentions the "already completed today" use case. The pause bypass is undocumented in help text. A first-time user who searches the help page won't confirm that --force bypasses the paused state — they have to trust the error message.
Where
src/cli.ts — the run command's --force option description (line ~324):
.option('--force', 'Force re-run squads that already completed today')
Fix
Update the description to cover both behaviors:
.option('--force', 'Force run: bypass paused state and re-run squads already completed today')
Labels
type:ux, priority:P2, squad:cli, source:ux-eval
Problem
When a user runs a paused squad, they see this error:
They are directed to use
--force. If they checksquads run --help, they see:The description only mentions the "already completed today" use case. The pause bypass is undocumented in help text. A first-time user who searches the help page won't confirm that
--forcebypasses the paused state — they have to trust the error message.Where
src/cli.ts— theruncommand's--forceoption description (line ~324):Fix
Update the description to cover both behaviors:
Labels
type:ux, priority:P2, squad:cli, source:ux-eval