From orchestrator
Displays orchestrator status dashboard with project progress bar and counts, phases, running tasks, blockers, recent activity, tech stack, checkpoints, and commands.
How this command is triggered — by the user, by Claude, or both
Slash command
/orchestrator:statusThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Orchestrator: Status Display the current project status from the orchestrator state. ## Instructions 1. Read the state file at `.claude/orchestrator/state/project.json` 2. If it doesn't exist, inform the user to run `/orchestrator:start` first 3. Display a comprehensive status dashboard ## Status Dashboard Format ## State File Schema The state file contains: ## Error Handling - If state file doesn't exist: Show message to run `/orchestrator:start` - If state file is corrupted: Suggest rollback to last checkpoint - If no tasks: Show planning phase status
Display the current project status from the orchestrator state.
.claude/orchestrator/state/project.json/orchestrator:start first╔═══════════════════════════════════════════════════════════════╗
║ ORCHESTRATOR STATUS ║
╠═══════════════════════════════════════════════════════════════╣
║ Project: [name] ║
║ Phase: [phase] ║
╚═══════════════════════════════════════════════════════════════╝
## Progress
[████████████░░░░░░░░] 60% (24/40 tasks)
| Status | Count |
|-------------|-------|
| ✓ Completed | 24 |
| → In Progress | 2 |
| ⚠ Blocked | 1 |
| ○ Pending | 13 |
## Current Phase: [implementation]
Phases:
✓ Ideation [complete]
✓ Specification [complete]
✓ Architecture [complete]
✓ Planning [complete]
→ Implementation [in_progress]
○ Testing [pending]
○ Deployment [pending]
## Currently Running
| Task | Agent | Started | Attempt |
|------|-------|---------|---------|
| TASK-025 | frontend-dev | 5m ago | 1 |
| TASK-026 | backend-dev | 3m ago | 1 |
## Blockers
⚠ TASK-019: External API not responding (3 attempts)
Since: 2h ago
Reason: Network timeout
## Recent Activity
- 10:45 ✓ TASK-024 completed (frontend-dev)
- 10:42 ✓ TASK-023 completed (backend-dev)
- 10:38 ✓ TASK-022 completed (test-engineer)
- 10:35 ✓ TASK-021 completed (frontend-dev)
- 10:30 🔖 Checkpoint CP-004 created
## Tech Stack
| Layer | Technology |
|----------|-------------------------|
| Frontend | React 19, TypeScript |
| Backend | Node.js, Hono |
| Database | PostgreSQL, Drizzle |
| Testing | Vitest, Playwright |
## Checkpoints
| ID | Time | Tasks | Commit |
|--------|---------|-------|---------|
| CP-004 | 10:30 | 20 | abc123 |
| CP-003 | 09:45 | 15 | def456 |
| CP-002 | 09:00 | 10 | ghi789 |
## Commands
- `/orchestrator:continue` - Resume autonomous development
- `/orchestrator:tasks` - View all tasks
- `/orchestrator:pause` - Pause after current task
- `/orchestrator:rollback CP-003` - Rollback to checkpoint
The state file contains:
{
"project": { "name": "...", "description": "..." },
"phase": "implementation",
"phases": { ... },
"techStack": { ... },
"tasks": [ ... ],
"currentTasks": [ ... ],
"progress": {
"total": 40,
"completed": 24,
"inProgress": 2,
"blocked": 1,
"percentage": 60
},
"blockers": [ ... ],
"checkpoints": [ ... ],
"history": [ ... ]
}
/orchestrator:startnpx claudepluginhub devsforge/orchestrator --plugin orchestrator/resumeLists active task orchestrations with progress and resumes specific ones via --date --project or --latest. Shows tasks in progress, blocked/next tasks, git activity, and quick actions.
/statusDisplays project status across tracks: active track, evaluate-loop step, task progress, pending tasks, last agent, other tracks, and next action.
/statusDisplays Conductor project status: verifies setup, summarizes track progress with task counts and percentages, and shows git branch/changes.
/pm-statusRenders ASCII progress dashboard for specified project showing phases, epics, progress bars, next tasks, blocked items, and Linear sync status; lists all projects otherwise. Supports --phase and --verbose flags.
/fire-dashboardDisplays a visual project dashboard showing current phase, milestone progress, breath execution, and validation status from .planning state files. Supports compact, watch, and JSON output modes.
/amoa-orchestration-statusDisplays orchestration phase progress: module completion, agent assignments, verification status. Supports verbose output, modules/agents only, JSON format, and custom project root.