← ClaudeAtlas

gabe-scope-changelisted

Scope evolution, one entry point. Classifies the requested change (Opus, 9 pivot-trigger rules): a PIVOT routes to /gabe-scope-pivot; an ADDITION executes inline (new REQs/SCs/phases/refs/constraints, decimal phase IDs, coverage re-check). Override with --force-addition or --force-pivot. Usage: /gabe-scope-change [--force-addition | --force-pivot] <description>
khujta/gabe-suite · ★ 0 · AI & Automation · score 63
Install: claude install-skill khujta/gabe-suite
# Gabe Scope Change — classify, then evolve ## Gabe execution contract (E1–E7) This skill runs under the suite execution contract — E1 EVIDENCE · E2 RUN-BEFORE-✅ · E3 NO SILENT DOWNGRADE · E4 REUSE FIRST · E5 STATE SYNC · E6 MISSING ANCHOR = STOP · E7 REPORT WHERE — floors, not ceilings; a skill's own gate may be stricter, never looser. Full text: `../gabe-docs/references/execution-contract.md` (if that file is missing, E6 applies — STOP). Single entry point for modifying a finalized SCOPE.md — its premise sections or its `## Phases` section alike. Classifies the requested change; **additions are executed by this skill's own Addition path** (Step 5); **pivots route to `/gabe-scope-pivot`**, which stays a separate skill on purpose — its `disable-model-invocation` flag structurally prevents a model from self-triggering a direction change, and a merged mode cannot carry that flag. **Why classifier-first and not user-picked?** Misclassifying a pivot as an addition corrupts version history. The classifier uses the declared 9 rules + Opus reasoning + rationale, so the user sees *why*. Overrides exist, but the default prevents silent scope corruption. > **Rendering note.** Output templates wrapped in bare triple-backtick fences are spec-meta delimiters — render as plain markdown at runtime. Tagged fences (```jsonl) stay fenced. See `gabe-docs/SKILL.md` § "Runtime output rendering convention". ## Procedure ### Step 1: Pre-flight - If `.kdbp/SCOPE.md` does not exist: exit with