stoplisted

# /ogre:stop Use this skill when the user wants to stop an active Ogre workflow (whole job or a single task), stop all workflows, archive runtime data, or delete runtime data. ## Concepts - **Job** = one feature/issue workflow, 1:1 with the issue. Id `job-<uuid>`. Stopping a job cascades: kills every `running` task under it and marks all its pending/running tasks `stopped`. - **Task** = one `ogre execute` attempt under a job. Id `task-<uuid>`. Stopping a single task kills just that pid/marks just that task `stopped` — sibling tasks and the job/issue state are untouched. Use job-level stop to abandon/pause the whole feature. Use task-level stop to kill one misbehaving background attempt (e.g. a hung `--background` execute) without aborting the rest of the workflow. ## Inputs Examples: - `/ogre:stop 107` (stop the job — cascades to all its tasks) - `/ogre:stop --job <job-id>` (same, addressed by job id) - `/ogre:stop --task <task-id>` (stop ONE task only) - `/ogre:stop --all` - `/ogre:stop 107 --archive` - `/ogre:stop 107 --delete` - `/ogre:stop 107 --list` **Flags are forwarded verbatim, never reinterpreted.** `-a`/`-A` (`--all`/`--archive`) differ only by case with very different blast radius (stop every job vs. archive one issue), so a wrong guess is silent (no parse error, just the wrong scope/action). 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. ##