add-conventionlisted

# add-convention Add a convention — but only after assessing whether it should exist and where it belongs. This skill is a gatekeeper and a router, not a stenographer. ## Step 0 — Preconditions and context 1. Confirm the repo is bootstrapped. 2. Read `CONVENTIONS.md` and `AGENTS.md` in full so you can detect overlap with existing rules and judge fit. ## Step 0.5 — Assessment (run first) Run the shared assessment protocol; the triage (Step 1) and routing (Step 2) questions are asked under it: - **Depth selector first.** Ask how deep this assessment should go: **express** — every choice takes its recommended default; only questions with no derivable default (the free-text essentials) are still asked; **guided** — only the questions marked high-impact below, plus the free-text essentials; **full** — every question below. If the repo's `CONVENTIONS.md` records an `Assessment depth:`, pre-select it as the recommended option — the selector always appears; a recorded depth is never applied silently. Otherwise recommend **full** when the request arrived with little or no context and **express** when it is already fully specified. At any question the operator may answer "defaults from here" or "go deeper"; honour the switch immediately. - Ask questions **one at a time**, each with a **recommended option** and a one-line reason; wait for each answer. - Use **structured selection** (single- or multiple-choice). If the host exposes a structured single-