/status
Update story status in the project tracking system and broadcast changes to agents via the message bus.
Quick Start
/agileflow:status STORY=US-0001 STATUS=in-progressParameters
| Parameter | Required | Default | Description |
|---|---|---|---|
STORY | Yes | - | Story ID (e.g., US-0001, US-0042) |
STATUS | Yes | - | New status: ready, in-progress, blocked, in-review, or done |
SUMMARY | No | - | 1-2 line summary of progress or reason for status change |
PR | No | - | Pull request URL (for review/done status) |
TO | No | ALL | Target agent(s) to notify via message bus |
Examples
Start Working on a Story
/agileflow:status STORY=US-0042 STATUS=in-progress SUMMARY="Beginning login form implementation"This updates the story status and notifies all agents that you've started work.
Mark as Blocked
/agileflow:status STORY=US-0045 STATUS=blocked SUMMARY="Waiting on AG-API to implement /auth/login endpoint"Broadcast the blocker so other team members can help resolve it.
Move to Code Review
/agileflow:status STORY=US-0038 STATUS=in-review PR=https://github.com/your-repo/pull/123 SUMMARY="Login form complete, ready for review"Share the PR link for reviewers.
Complete a Story
/agileflow:status STORY=US-0030 STATUS=done SUMMARY="User registration fully tested and deployed"Mark the story as finished.
Output
The command displays:
- Diff Preview - Shows what will change in
docs/09-agents/status.json - Confirmation - YES/NO prompt to apply changes
- Success Message - Confirmation that status updated
- Message Bus Entry - Broadcast message sent to agents
Example output:
✅ Story Status Updated
Story: US-0042
Status: ready → in-progress
Summary: Beginning login form implementation
Updated: 2025-12-24T14:30:00Z
Message broadcast to: ALL agentsData Files Updated
This command modifies:
docs/09-agents/status.json- Story status trackingdocs/09-agents/bus/log.jsonl- Agent message bus (appends status change event)
Status Values Explained
- ready - Story is prepared and waiting to be started
- in-progress - Currently being actively worked on
- blocked - Waiting on external dependency or clarification
- in-review - Complete and awaiting code review/approval
- done - Finished, tested, and verified
Best Practices
- Always include a summary - Helps team understand context and progress
- Update immediately - Don't wait to batch status updates
- Link PRs for reviews - Helps reviewers find your work
- Use clear language - Explain blockers in detail so others can help
- Update when blocked - Don't silently sit on blockers - communicate immediately
Related Commands
/agileflow:board- View kanban board with all statuses/agileflow:blockers- Analyze and resolve blockers/agileflow:assign- Assign story to owner with status/agileflow:metrics- Track completion metrics