skill-author

# skill-author Author a new skill, the right way. Routed to when the user invokes `/new-skill "<gap>"`. ## Pre-flight Read these, or STOP and surface the gap — never author on assumption: - The `<gap>` argument. Absent → STOP and ask: "Describe the gap this skill would fill. What situation does no existing skill cover today?" - `${CLAUDE_PLUGIN_ROOT}/routines/INDEX.md` — the surface scan of every existing skill. This is the gap-overlap check in Phase 1 and the integration target in Phase 5. Never bulk-read the skill bodies. - `${CLAUDE_PLUGIN_ROOT}/routines/commit-gate/SKILL.md` and `${CLAUDE_PLUGIN_ROOT}/routines/tdd/SKILL.md` — the canonical v2 format the authored skill must mirror. Read them before Phase 3. - `<project-root>/.codearbiter/CONTEXT.md` — project context, only if the gap is project-specific. A generic skill needs no project state. ## Phase 1 — Gap evidence · gate: BLOCK A new skill is permanent surface area. It is not written until the gap is proven real and proven uncovered. Restate the gap in one sentence. Then scan `INDEX.md` for overlap: if an existing skill's "Owns" column already covers this, STOP and name it — "The `<name>` skill already owns this; review it before requesting a new one." If no skill covers it, demand evidence — one of: - **A** — three specific cases where the gap blocked work: what was attempted, what happened with no skill, what it cost. - **B** — one high-impact case with traceable evidence: a blocked PR, an introduced defect...