status

You can get a development session status diagnostic by aggregating spec progress, phase statuses, active blockers, and next steps into a unified read-only view. It scans spec files, phase files, task files, and turn history to deliver a snapshot of session health.

Tracking spec progress and blockers is handled by aggregating data from session/spec.md, session/phases/*.md, and session/tasks/*.md. It enforces read-only behavior to protect state while formatting the output into summary, detail, blockers, and requirements views.

You can view specific development blockers using the blockers mode, which filters the aggregated session diagnostic to isolate active blockers. This prevents the need to manually parse through changelog, decisions, and turn history files.

The session status diagnostic does not modify task or spec files because it enforces strict read-only behavior. This design protects your session state while reading from spec, phase, task, changelog, and decisions files to generate its output.

Checking phase status and upcoming steps is done by reading session/phases/*.md and session/tasks/*.md to map completion and identify next actions. It provides an auditable trail of decisions and changelog history to inform your upcoming workflow steps.