plan-protocollisted

# Plan Protocol — installer This skill **installs** the protocol. It is never the protocol itself. That distinction is load-bearing: skills only fire in Claude Code. If enforcement lived in a skill, Codex, Cursor and Windsurf would ignore it entirely — the exact single-runtime gap the protocol was written to close. So the teeth are a **git hook** plus a **dependency-free engine**, both committed to the repo, and this skill is how they get there. ## What the protocol is **No plan on `main`, no code.** Every task declares, in `meta.yaml` merged to the base branch, which paths it will touch. `guard` then fails any push or gate run that changes a path outside that declaration. Scope growth becomes a visible edit to the plan instead of silent PR bloat. Full protocol: `AGENTS.md` at the repo root. ## The engine One file, `.specify/extensions/plan-protocol/plan.mjs`. `node:` builtins only — no `tsx`, no build step, no `npm install`, no `package.json` required anywhere. Plain `node` is present on every machine already running a coding agent; a devDependency in one subdirectory of one repo is not. ```bash node .specify/extensions/plan-protocol/plan.mjs <verb> ``` | Verb | Does | |---|---| | `index` | regenerate the registry from every `meta.yaml` | | `check` | validate metas + registry freshness (gate step) | | `sync` | SYNC: overlap and migration-number conflicts vs the base ref | | `guard` | blast-radius cap (gate step + pre-push hook) | | `submit` | plan-only fast lane: pus