status

# `status` — Plan State Reader Three variants for different contexts. All backed by `scripts/dev/active_plan.py`. --- ## Variants ### `status [feature]` — Full state The full picture: which plan file is active, its goal, progress (X/N tasks complete), and the next unchecked task block. **Script invocation:** ```bash # With a feature name (from $ARGUMENTS or conversation context): uv run python scripts/dev/active_plan.py --feature <slug> # Without a feature name (uses root PLAN.md): uv run python scripts/dev/active_plan.py ``` **Return:** the complete script output verbatim. **When to call:** - Starting a session: "where did we leave off?" - After completing a task: "what comes next?" - Before adding scope: "does this belong to the current plan?" --- ### `next [feature]` — Next task only The single next unchecked task block. No header noise. **Script invocation:** same as `status`. **Return:** only the content from `--- Next task ---` onward. Drop the Plan / Title / Goal / Progress header lines entirely. If no `--- Next task ---` separator is present (root PLAN.md mode), return the full script output — the phase block is already task-level content. If the script output contains "All steps complete", say so and suggest: - `/gflow:changelog` to review unreleased changes - `/gflow:release` if the phase is fully done **When to call:** - "What do I do right now?" — between tasks, no orientation needed - Resuming mid-session after a context switch --- ### `active`...