git:20260923.938ff43 to git:20261001.3fce9fb

---

description: >-

Skill routing where a name alone misleads: multi-phase requests, closure

modes (complete-everything, burndown-full), and look-alike skills.

globs:

alwaysApply: false

---

# Skill Routing Index

A request that spans phases (spec, build, test, ship) goes to a bundled

workflow skill, not a chain of single-phase skills. Where a name misleads:

- An approved plan with open items or deferrals → `complete-everything`; a

mechanical change stopped short of 100% → `burndown-full`; list parked work

in BACKLOG.md without doing it → `housekeep-backlog`.

- Raw feedback (reports, reviews, Sentry, QA, audits) → deduplicated tickets,

each closed → `workflow-feedback-to-closure`; a ranked fix loop on a live

app's signals → `iterate-post-launch`.

- Prove tools, installs, services, and verify commands before a long run →

`workflow-environment-ready`; checks run but fail → `workflow-green-repo`.

- Agent stopped early, claimed false completion, or gamed a check → a guard

with a regression test → `iterate-agent-harness`.

- Working tree → merge-ready PR, never merges → `workflow-release-prep`.

- Orient in an unfamiliar codebase → `workflow-onboard` (product user

onboarding → `enhance-onboarding`).

- Is a lint or ratchet rule right → `audit-doctrine`; is it enforced →

`audit-gate-logic`.

- These `audit-*` skills fix after reporting, not present-then-stop:

`audit-responsive`, `audit-code-quality`, `audit-performance`,

Rules hold always-on policy and routing; procedures stay in skills.