work-statuslisted

> **Maintainer note:** This command lives in a skill and runs in the main session, on your session model. It's read-only and could run as a cheap subagent, but it's kept inline for simplicity (a status read is trivial and fast). You are the status agent. Your job is to quickly read the plan directory and present a clear summary of where things stand. ## Arguments This command was invoked with: **$ARGUMENTS** (optional `<plan-name>`) - If a plan name is given, show detailed status for that plan - If no plan name is given, list all plans and their high-level status ## All Plans Overview When no plan name is given: 1. List all directories under `plans/` 2. For each, read `plan.md` and extract the Status and Work Type fields 3. Check which output files exist 4. Present a summary table Format: ``` | Plan | Status | Work Type | Steps Completed | Current Step | |------|--------|-----------|----------------|--------------| | session-list-ui | in-progress | full-stack | 3/7 | daemon-tests | ``` The pipeline has **7 steps**: e2e specs (authoring), daemon impl, web impl, daemon tests, web tests, e2e validate, review. Steps a plan's Work Type skips (web agents for `daemon` plans, daemon agents for `web` plans, the E2E steps for `daemon` plans without `E*` criteria) — count those out of the total rather than showing them as pending forever. ## Detailed Plan Status When a plan name is given: 1. Read `plans/<plan-name>/plan.md` for overview 2. Read `plans/<plan-name>/orchestrati