Skip to content
Apothem
Command pipeline

/plan-status

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

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/] [--verbose]

Inputs

Any plan suite at any lifecycle state — reads PROGRESS.md, PLAN-NOTES.md, MASTER-PLAN.md, and the phases/ reports.

Outputs

A strategic status report written to the operator's output stream. This command is read-only — it creates and modifies no files.

Downstream

Used standalone for progress inspection — orthogonal to the canonical sequence, invocable read-only at any point.

Workflow phases

The command is read-only — it reads the suite's tracking files and reports; it writes nothing:

  1. Load context — Read PROGRESS.md, PLAN-NOTES.md, MASTER-PLAN.md, and scan phases/ for existing reports.
  2. Assess status — Survey the task / phase / artifact dimensions and read the Resumption Contract.
  3. Emit the status report — Present completion status, the phase tracker, and strategic analysis directly to the operator.
  4. Spot-check — With --verbose, grade suite health and cite spot-check evidence (markdown links, line ranges, commit SHAs) against existing files without modifying any.

Failure modes

SymptomCauseRecovery
Required tracking file missingPlan suite incompleteSurface the gap as a finding; run /plan-generate to create the suite
Malformed tracking fileSection truncated or unparseableName the absence / contradiction in the report; repair routes to the writeful commands
Field absent or contradictory across filesTracking driftReport the contradiction explicitly; do not synthesize the missing value

Examples

# Report on the most recent plan suite
/plan-status

# Verbose health-grade against a named plan suite
/plan-status path/to/plan-suite/ --verbose

Cross-references

On this page