statuslisted

# /ogre:status Use this skill when the user wants to see current Ogre workflow progress. ## Inputs Examples: - `/ogre:status` - `/ogre:status 107` - `/ogre:status --job <job-id>` (issue state, addressed by job id instead of issue slug) - `/ogre:status --tasks` (all tasks across all jobs/issues) - `/ogre:status 107 --tasks` (tasks for one issue/job) - `/ogre:status --task <task-id>` (single task record) - `/ogre:status --watch` (live-refresh, run standalone in another terminal while a task is executing — Ctrl-C to quit) - `/ogre:status --watch --interval 5` (custom refresh seconds, default 2) **Flags are forwarded verbatim, never reinterpreted.** `-t`/`-T` (`--task`/`--tasks`) differ only by case and a trailing letter, with different scopes (one task vs. every task), so a wrong guess is silent (no parse error, just the wrong scope). If the user's own message names an actual flag/short-form, pass that exact token through unchanged rather than guessing a different one you assume is equivalent. ## Concepts - **Job** = one feature/issue workflow, 1:1 with the issue. Id `job-<uuid>`, stored as `job_id` in that issue's state json. - **Task** = one checklist step under a job's plan. Id `task-<uuid>`, in the shared ledger `.ai/.ogre/state/tasks.json`, `step`/`step_index` hold the checklist text and its 1-based position. Seeded automatically the moment the plan is synced (on any `status`/`task-list`/`execute` call) — exists and shows `pending` even before anyone runs `execute` a