cortex-looplisted

# cortex-loop ## When to use **This skill is callable-only** — it carries no trigger surface in the skill listing and is not routed into automatically. It is reached two ways, both of which name it explicitly: - the five scheduled-task payloads Cortex writes itself (`src/cli/templates.ts` `SCHEDULED_TASKS`), each of which names this skill and the reference file for the member it is running; - a developer invoking `/cortex-loop` and naming the loop. A loop is also runnable without this skill at all: every one has a deterministic CLI verb (`cortex loop-spec-drift`, `cortex pulse-hygiene`, …) that needs no routing. Reach for the CLI when you want the loop's mechanical half and no judgment. ## Dispatch Read **one** reference file — the loop you were asked to run — and follow it exactly. Do not read the others; they are unrelated work and cost context you will not use. If the caller named a loop not in this table, say so and stop rather than guessing the nearest match. | Loop | Reference | CLI verb | Writes | |---|---|---|---| | `hygiene` | `references/hygiene.md` | `cortex pulse-hygiene` | `.cortex/pulse/reports/hygiene.md` | | `bug-triage` | `references/bug-triage.md` | `cortex loop-bug-triage` | `.cortex/pulse/reports/bug-triage.md` | | `spec-drift` | `references/spec-drift.md` | `cortex loop-spec-drift` | `.cortex/pulse/reports/spec-drift.md` | | `rule-decay` | `references/rule-decay.md` | `cortex loop-rule-decay` | `.cortex/pulse/reports/rule-candidates.md` | | `on