capability-upgradelisted

# /capability-upgrade — Compatibility Route (Phase 1) This Skill is a thin compatibility entry for the **old** Capability Pack flow. New capability work uses **`$capability-builder create`**. The deep research material from the previous version is preserved as a conditional reference and is not loaded by default. ## Routing - **New capability work** (new domain, new pack-style request, YAML domain pack mention) → **use `$capability-builder create`** per `.claude/skills/capability-builder/SKILL.md` and its mandatory `references/create-protocol.md`. That path creates exactly one project-owned Agent Skill at `.agents/skills/<name>/`, validates, behavior-proves, and projects to `.claude/skills/<name>/`. - **Existing project Skill change** (you already have `.agents/skills/<name>/` and want to evolve it) → **future `$capability-builder evolve`** (Phase 2, not in this release). Record `STOPPED_WITH_REASON: evolve is Phase 2` and stop. No writes. - **Existing legacy Capability Pack edit** (`.tad/capability-packs/<name>/` maintenance, retiring, converting, or editing a pack in the old tree) → **STOP `LEGACY_PACK_OUT_OF_SCOPE`**. Phase 1 neither retires nor edits legacy packs. No writes. Ask the human to choose a separately scoped legacy-maintenance task or a new project-owned Skill. Do not silently reinterpret a pack upgrade as Skill creation. - **General capability routing question** (which pack for a task? `pack-collisions.yaml` gap) → read pack registry / collision file inside