Status
Check the current status of tasks in the orchestration system with various filtering and reporting options.
npx claude-code-templates@latest --command orchestration/status Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Task Status Command
Check the current status of tasks in the orchestration system with various filtering and reporting options.
Usage
/task-status [options]Description
Provides comprehensive visibility into task progress, status distribution, and execution metrics across all active orchestrations.
Command Variants
Basic Status Overview
/task-statusShows summary of all tasks across all active orchestrations.
Today's Tasks
/task-status --todayShows only tasks from today's orchestrations.
Specific Orchestration
/task-status --date 03_15_2024 --project payment_integrationShows tasks from a specific orchestration.
Status Filter
/task-status --status in_progress
/task-status --status qa
/task-status --status on_holdShows only tasks with specified status.
Detailed View
/task-status --detailedShows comprehensive information for each task.
Output Formats
Summary View (Default)
Task Orchestration Status Summary
=================================
Active Orchestrations: 3
Total Tasks: 47
Status Distribution:
┌─────────────┬───────┬────────────┐
│ Status │ Count │ Percentage │
├─────────────┼───────┼────────────┤
│ completed │ 12 │ 26% │
│ qa │ 5 │ 11% │
│ in_progress │ 3 │ 6% │
│ on_hold │ 2 │ 4% │
│ todos │ 25 │ 53% │
└─────────────┴───────┴────────────┘
Active Tasks (in_progress):
- TASK-001: Implement JWT authentication (Agent: dev-frontend)
- TASK-007: Create payment webhook handler (Agent: dev-backend)
- TASK-012: Write integration tests (Agent: test-developer)
Blocked Tasks (on_hold):
- TASK-004: User profile API (Blocked by: TASK-001)
- TASK-009: Payment confirmation UI (Blocked by: TASK-007)Detailed View
Task Details for: 03_15_2024/authentication_system
==================================================
TASK-001: Implement JWT authentication
Status: in_progress
Agent: dev-frontend
Started: 2024-03-15T14:30:00Z
Duration: 3.5 hours
Progress: 75% (est. 1 hour remaining)
Dependencies: None
Blocks: TASK-004, TASK-005
Location: /task-orchestration/03_15_2024/authentication_system/tasks/in_progress/
Status History:
- todos → in_progress (2024-03-15T14:30:00Z) by dev-frontendTimeline View
/task-status --timelineShows Gantt-style timeline of task execution.
Velocity Report
/task-status --velocityShows completion rates and performance metrics.
Filtering Options
By Agent
/task-status --agent dev-frontendBy Priority
/task-status --priority highBy Type
/task-status --type feature
/task-status --type bugfixMultiple Filters
/task-status --status todos --priority high --type securityQuick Actions
Show Critical Path
/task-status --critical-pathHighlights tasks that are blocking others.
Show Overdue
/task-status --overdueShows tasks exceeding estimated time.
Show Available
/task-status --availableShows todos tasks ready to be picked up.
Integration Commands
Export Status
/task-status --export markdown
/task-status --export csvWatch Mode
/task-status --watchUpdates status in real-time (refreshes every 30 seconds).
Examples
Example 1: Morning Standup View
/task-status --today --detailedExample 2: Find Blocked Work
/task-status --status on_hold --show-blockersExample 3: Agent Workload
/task-status --by-agent --status in_progressExample 4: Sprint Progress
/task-status --date 03_15_2024 --metricsMetrics and Analytics
Completion Metrics
- Average time per task
- Tasks completed per day
- Status transition times
Bottleneck Analysis
- Most blocking tasks
- Longest on_hold duration
- Critical path duration
Agent Performance
- Tasks per agent
- Average completion time
- Current workload
Best Practices
- Daily Check: Run
/task-status --todayeach morning - Blocker Review: Check
/task-status --status on_holdregularly - Progress Tracking: Use
/task-status --velocityfor trends - Resource Planning: Monitor
/task-status --by-agent
Notes
- Status data is read from TASK-STATUS-TRACKER.yaml files
- All times are shown in local timezone
- Completed tasks are included in metrics but not in active lists
- Use
--allflag to include historical orchestrations