Skip to content

/plan-status

Role: Reporter Pipeline position: read-only

Read-only plan-suite progress reporter — emits status without modifying any files.

Canonical invocation

/plan-status

With arguments:

/plan-status [path/to/plan-suite/] [phase-id] [--dry-run]

Inputs

Any plan suite at any lifecycle state

Outputs

Status report to stdout (no file writes)

Downstream

Used standalone for progress inspection

Workflow phases

The command follows the standard /plan-* pipeline workflow:

  1. Load context — Read plan suite, rules, and Resumption Contract.
  2. Verify prerequisites — Confirm dependency phases complete.
  3. Execute tasks — Perform the command mission.
  4. Verify outputs — Confirm all declared outputs exist and pass quality gates.
  5. Update PROGRESS.md — Record verified outputs in the Phase Output Registry.
  6. Emit REPORT.md — Pre-emission gate attestation recorded.

Failure modes

Symptom Cause Recovery
Prerequisite incomplete Dependent phase not finished Complete upstream phase first
Quality gate FAIL Output does not meet standards Fix the output and re-run
Missing input file Plan suite file absent Run /plan-generate to create it

Examples

# Dry-run to preview what would happen
/plan-status --dry-run

# Execute against a named plan suite
/plan-status path/to/plan-suite/

Cross-references