opslisted

Execute a milestone's interactive 🔧 Operational and 🔎 Investigation tasks — the judgment-bound work that is NOT auto-dispatched. Two modes in one pass: Operational changes production/environment state through a sanctioned surface (config/catalog/entity authoring, backfills, alarm config, dependency installs, session/machine setup); Investigation produces a defensible decision from live data (diagnoses, spikes, zero/anomaly triage) and files follow-on tasks. Enforces: autonomous runs STAGE (never verdicts, never ✅ Done), read-only diagnosis before any write, falsify every "it's fine", audited read-modify-write, reconcile+capture, "Done ≠ deployed ≠ seeded ≠ working". Records durable research to a staging journal. Use when the user says "work the ops tasks", "run ops/tooling for milestone X", "work the operational/investigation tasks", or starts an overnight or interactive ops run on a project's task board.
phahadek/claude-orchestrator · ★ 1 · AI & Automation · score 74

Install: claude install-skill phahadek/claude-orchestrator

# ops — execute a milestone's Operational & Investigation tasks Companion to `groom` (backlog→Ready) and `design` (design tasks): this skill *works* the 🔧 **Operational** and 🔎 **Investigation** tasks — the interactive, judgment-bound ones that are **not** auto-dispatched. Its whole value is a verification discipline that refuses to trust premises, statuses, or convenient shortcuts, and that **treats an unattended pass as staging, never as conclusions.** Follow it even when a task "looks like a one-liner." This skill shares its planning-procedure core with `/groom` and `/design` — see `../_shared/reference/hard-rules.md` (canonical source `packages/backend/src/planning/procedureCore.ts`) for the rules this skill also follows: **deterministic load, not hand-fetch** (Flow step 2 below), **the human/operator is the gate** (see § Status handling), and **no silent writes** (verdicts land on the journal, never the task page, until the operator confirms). > Scope: this skill runs 🔧 Operational + 🔎 Investigation, **plus observational / E2E 🧪 Testing > folded in as an Investigation variant** (run the system live → a **disposition**: `pass` / > `blocked-pending-fix` / `pass-with-caveat` — there is no "fail"). > **Test-authoring 🧪 Testing** (writing test code, no live-data dependency) and 📝 Docs stay out — > the former is really 💻 Code, so reclassify it (the loader lists any it caught in `test_authoring`; > flag the rest at triage). (Legacy 🛠️ Tooling tasks that predate the