feat(projman): harden sprint approval gate with --force override
- sprint-approval.md: approval is now a hard block, not a warning - sprint-start.md: added --force flag documentation - orchestrator.md: approval verification is now a hard stop - docs: updated commands cheatsheet BREAKING: /sprint-start now requires approval or --force flag Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -24,11 +24,14 @@ Initiate sprint execution. The orchestrator agent verifies approval, analyzes de
|
||||
|
||||
Run `/sprint-start` when ready to begin executing a planned sprint.
|
||||
|
||||
**Flags:**
|
||||
- `--force` — Bypass approval gate (emergency only, logged to milestone)
|
||||
|
||||
## Workflow
|
||||
|
||||
Execute the sprint start workflow:
|
||||
|
||||
1. **Verify Sprint Approval** (recommended) - Check milestone for approval record
|
||||
1. **Verify Sprint Approval** (required) - Check milestone for approval record. STOP if missing unless `--force` flag provided.
|
||||
2. **Detect Checkpoints** - Check for resume points from interrupted sessions
|
||||
3. **Fetch Sprint Issues** - Get open issues from milestone
|
||||
4. **Analyze Dependencies** - Use `get_execution_order` for parallel batches
|
||||
|
||||
Reference in New Issue
Block a user