ratify-ruleslisted

# /ratify-rules — Lesson → Rule Ratification (operator-gated) The retro loop **proposes**; this skill **lands**. `sprint-retro-author` writes recurring lessons into a retro's `## Candidate A-rules` section but — by design — never edits `brain-hot.md` itself (A-rules are never auto-applied). This skill is the operator's ratification gate: it gathers those candidates, you decide on each, and the approved ones become permanent project rules (`A011+`). That closes the loop from *lesson observed* → *lesson enforced*. ## Token budget (MANDATORY) - `Grep` `docs/spec/retros/sprint-*.md` for `## Candidate A-rules` — do NOT full-Read every retro. Read ONLY the candidate section of each retro that has one (offset Read around the grep hit). - One `Read` of `.claude/rules/brain-hot.md` (the `## Project-specific rules` section) to find the next free `A###` and check for duplicates. - `Grep` `lesson-trigger-map.md` for an existing row before adding one. - No subagents — this is a short interactive edit, not an exploration. ## Usage - `/ratify-rules` — scan all retros for un-landed candidates, decide on each - `/ratify-rules S<N>` — scope to a single sprint's retro - `/ratify-rules A0##` — land one specific candidate by its proposed number ## Steps 1. **Gather candidates.** `Grep -n '## Candidate A-rules'` `docs/spec/retros/sprint-*.md`. For each hit, Read just that section. A candidate already marked `ratified → A0##` or `dropped — …` is **done** — skip it. The live se