/workflow-status - View Workflow Progress

View current status and progress of active workflows.

Usage

/workflow-status [workflow-name] [--options]

Arguments:

• workflow-name - Specific workflow to check (optional)
• --all - Show all workflows including completed
• --detailed - Show step-by-step details
• --blocked - Show only blocked workflows

Examples

/workflow-status
/workflow-status requirements-to-stories
/workflow-status --blocked
/workflow-status development --detailed

What It Shows

Default View

• All active workflows
• Current step and agent
• Progress percentage
• Blockers if any

Detailed View

• Each step with timing
• Decisions made per step
• Artifacts created
• Full execution trace

Output Format

## Active Workflows

### 1. Requirements to Stories
**Trigger:** Feature request - User Authentication
**Status:** 🔄 In Progress
**Progress:** ████████░░ 66%

✅ Orchestrator Receives (5m) ✅ BA Analyzes (25m) ✅ PO Validates (15m) 🔄 Architect Reviews (in progress - 10m) ⏳ QA Reviews ⏳ Orchestrator Finalizes

**Current:** Software Architect reviewing technical feasibility
**Artifacts:** PROJ-101, 102, 103, BRD-Auth
**Est. Remaining:** 20 minutes

---

### 2. Development
**Trigger:** PROJ-089 marked Ready for Dev
**Status:** 🚫 Blocked
**Progress:** ████░░░░░░ 40%

✅ Senior Dev Breakdown (30m) ✅ Implementation (4h) 🚫 Code Review (blocked) ⏳ QA Testing ⏳ DevOps Deploy ⏳ PO Acceptance

**Blocker:** Waiting for API spec from external team
**Blocked Since:** 2 hours
**Impact:** Sprint delivery at risk

---

### Summary

| Status | Count |
|--------|-------|
| In Progress | 2 |
| Blocked | 1 |
| Completed Today | 3 |

### Blockers Requiring Attention
1. **PROJ-089:** API spec needed - escalate to stakeholder?

Detailed View Format

## Workflow: Requirements to Stories

### Execution Trace

#### Step 1: Orchestrator Receives
**Agent:** Orchestrator
**Started:** 09:00 | **Completed:** 09:05 | **Duration:** 5m

**Input:**
> Feature request: User authentication for mobile app

**Actions:**
1. Acknowledged receipt
2. Classified as new feature
3. Routed to Business Analyst

**Output:** Request routed to BA

---

#### Step 2: Business Analyst Analyzes
**Agent:** Business Analyst
**Started:** 09:05 | **Completed:** 09:30 | **Duration:** 25m

**Decisions:**
- DEC-039: Clarification questions needed (3 questions)
- DEC-040: Split into 3 user stories

**Artifacts Created:**
- PROJ-101: Login flow
- PROJ-102: Registration flow
- PROJ-103: Password reset
- Confluence: BRD updated

**Handoff:** → Product Owner

---

[continues for each step...]

Skill Used

observability-workflow-trace

Related Commands

• /activity - Detailed activity log
• /decisions - Decision trail
• /trace PROJ-123 - Trace for specific ticket