Plan Status Command

Display the current state of orchestration from .claude/plan.json.

Invocation

When user invokes /plan-status:

Steps

1. Check if .claude/plan.json exists

   • If not: Report "No active orchestration. Use /orchestrate to start."

2. Read and parse plan.json

3. Display status summary:

## Orchestration Status

**Original Task**: {orchestrator.original_task}
**Status**: {orchestrator.status}
**Provider**: {orchestrator.provider} / {orchestrator.model}
**Mode**: {orchestrator.mode}

## Subtasks

| # | Title | Status | Iteration | Last Update |
|---|-------|--------|-----------|-------------|
| 1 | {title} | {status} | {current}/{max} | {last progress summary} |
| 2 | {title} | {status} | {current}/{max} | {last progress summary} |
...

## Summary

- Total: {total} subtasks
- Completed: {completed count}
- In Progress: {in_progress count}
- Pending: {pending count}
- Skipped: {skipped count}
- Failed/Blocked: {failed + blocked count}

4. If any subtask is in_progress, show its latest progress entries

5. If orchestration is completed or cancelled, mention cleanup status

Example Output

## Orchestration Status

**Original Task**: Build a Node.js REST API with authentication
**Status**: in_progress
**Provider**: claude / sonnet
**Mode**: auto

## Subtasks

| # | Title | Status | Iteration | Last Update |
|---|-------|--------|-----------|-------------|
| 1 | Set up project structure | completed | 3/20 | All setup complete |
| 2 | Implement auth endpoints | in_progress | 5/20 | Working on JWT validation |
| 3 | Implement CRUD endpoints | pending | -/20 | - |
| 4 | Add tests | pending | -/20 | - |

## Current Progress (subtask-002)

- Iteration 1: Created auth controller skeleton
- Iteration 2: Implemented register endpoint
- Iteration 3: Implemented login endpoint
- Iteration 4: Added password hashing
- Iteration 5: Working on JWT validation

## Summary

- Total: 4 subtasks
- Completed: 1
- In Progress: 1
- Pending: 2