---
description: >-
  Skill routing index for cursor-kenji. Consult when choosing between an
  individual skill and a bundled workflow, when a request spans multiple
  phases (spec + build + test, launch + verify + iterate), or when entering
  a closure mode (complete-everything, burndown-full).
globs:
alwaysApply: false
---

# Skill Routing

Skills load on demand and self-describe — never inline skill content into a
rule. Full catalog: each skill's own description, plus `docs/PLAN-LOOPS.md`
for the plan-loop sequences.

## Use a bundled workflow when the request spans phases

- Build a feature end-to-end → `workflow-build-feature`
- Fix a bug and ship it → `workflow-fix-and-ship`
- Pre-release quality check → `workflow-quality-gate`
- Local working tree → merge-ready PR (do not merge) → `workflow-release-prep`
- Full launch preparation → `workflow-launch-ready`
- Orient to a new codebase → `workflow-onboard`
- Post-launch feedback loop → `iterate-post-launch`
- Deploy and observe / roll back → `workflow-ship-and-observe`
- Drive the whole repo to green → `workflow-green-repo`
- Finish a partial burndown to 100% → `burndown-full`
- Close a plan with zero deferrals → `complete-everything`
- Inventory parked work into a living BACKLOG.md → `housekeep-backlog`
- Current-year docs + gap analysis before a non-trivial change → `research`
- Preflight the environment → `workflow-environment-ready`
- Feedback to durable tickets → `workflow-feedback-to-closure`
- Feature-flag rollout → `workflow-feature-flag`
- Convert an agent failure into a guard → `iterate-agent-harness`

Highest-impact prove combo: `test-exploratory` → `workflow-feedback-to-closure` → `test-playwright`. Optional pre-gate: `test-exploratory` then `workflow-quality-gate`. Pre-release trio: `housekeep-backlog` → `workflow-release-prep` → `docs-adr`. Doctrine vs enforcement: `audit-doctrine` (is the rule right) × `audit-gate-logic` (is it enforced) → `housekeep-gates` / `housekeep-backlog`.

## Use an individual skill when scoped to one phase

Names are predictable: `plan-*` (audit → approved burndown, no fixes),
`audit-*` (findings; default present-then-stop), `enhance-*` (apply
improvements), `test-*`, `debug-*`, `deploy-*`, `design-*`, `backend-*`,
`mobile-*`. Upgrade *how* an existing skill instructs (not what it does) →
`enhance-skill-prompts`. State the task; the matching skill self-selects by
description.

**Audit-and-fix exceptions** (report, then implement): `audit-responsive`,
`audit-code-quality`, `audit-performance`, `audit-security`, `audit-i18n`,
`audit-bundle-size`. `enhance-email-deliverability` is also audit-and-fix.
Do not treat those as present-then-stop.

## Closure modes

`complete-everything` and `burndown-full` persist their state files and
continue through phase checkpoints. Before either claims completion, apply
`verification-before-completion` and invoke the `completion-judge` subagent.

## Rules vs skills

Rules are always-on policy and routing only; skills are on-demand
procedures. Never promote a skill's workflow into an always-on rule.