$manage-status
Reads from:
.workflow/state.json— project-level state machine.workflow/roadmap.md— milestone and phase structure.workflow/scratch/*/index.json— per-phase metadata and progress (resolved via state.json artifact registry).workflow/scratch/*/.task/TASK-*.json— individual task statuses (resolved via state.json artifact registry).workflow/wiki-index.json— unified wiki graph index (entry counts, health)
Output boundary: Read-only command. MUST NOT write any files. All output is displayed to the user via text.
Phase Gates (MANDATORY, BLOCKING)
GATE 1: Load → Render (State loading → Dashboard display)
- REQUIRED:
.workflow/exists andstate.jsonis readable (E001/E002 if not). - REQUIRED: Project state loaded with milestone and artifact registry.
- BLOCKED if state.json missing or corrupt (E002).
GATE 2: Render → Route (Dashboard → Next-step suggestions)
- REQUIRED: Dashboard sections rendered with available data.
- REQUIRED: Next-step suggestion computed from state decision table.
- BLOCKED: never — graceful degradation for missing sections.
Step 1: Validate Project
Verify .workflow/ exists (E001) and state.json is present (E002).
Step 2: Load State Files
Read: state.json, roadmap.md, per-phase scratch/*/index.json, task files scratch/*/.task/TASK-*.json (all resolved via artifact registry).
Step 3: Calculate Progress
For each phase directory found:
- Count total tasks, completed, failed, blocked, pending
- Calculate completion percentage
- Determine phase status from index.json
Step 4: Render Dashboard
Display sections: Milestones & Phases (per-phase status, progress bars, completion %), Active Work (in-progress and blocked tasks), Knowledge Graph (wiki entry counts by type, health score, orphans), Next Steps (state-based suggestion).
Step 5: Suggest Next Steps
Use this decision table to suggest the next action:
| Current State | Suggestion |
|---|---|
| No phases planned | $maestro-brainstorm or $maestro-plan |
| Phase planned, not executed | $maestro-execute "<N>" |
| Phase executed, not reviewed | $quality-review "<N>" |
| Phase reviewed PASS/WARN | $quality-test "<N>" |
| UAT passed | $maestro-milestone-audit |
| All milestone phases done | $maestro-milestone-audit |
<error_codes>
| Code | Severity | Description |
|---|---|---|
| E001 | fatal | .workflow/ not initialized -- run $maestro-init first |
| E002 | fatal | state.json missing or corrupt |
| </error_codes> |
<success_criteria>
-
.workflow/andstate.jsonvalidated - All state sources loaded (state.json, roadmap, phase indexes, task files)
- Progress calculated per phase (total, completed, failed, blocked, pending, percentage)
- Dashboard rendered with milestones, phases, active work, and next steps
- Next step suggestion matches current project state via decision table </success_criteria>