ticket-gate-referencelisted

Reference material the ticket-gate agent reads once per run: the review output template it composes, the specialist lens definitions with their result contract, the comment templates it posts, and the `forge_*` call mapping every forge operation looks up. Preloaded into ticket-gate through that agent's `skills:` frontmatter. Not a standalone workflow: it decides nothing, and the only rules it carries are the ones a lens itself obeys.
agigante80/forge-kit · ★ 0 · AI & Automation · score 60

Install: claude install-skill agigante80/forge-kit

# ticket-gate reference **`ticket-gate.md` is canonical for every ORCHESTRATOR rule.** It carries the artifacts that agent reads once per run: an output template, the lens briefs, the comment templates and the `forge_*` call mapping. The dividing line is who obeys a rule: a rule the LENS follows travels with its brief below, because the brief is dispatched to the lens verbatim; every rule ticket-gate itself follows (when a lens runs, how results merge, what a re-run rescopes) stays there and is only POINTED at from here. Nothing is restated across the two, because this repo's own record is that content copied into a second location drifts from the first (the lens contract across two plugins, the doc-versus-gate restatement). If a rule appears both here and in `ticket-gate.md`, that is the bug, and `ticket-gate.md` wins. Agents cannot carry a `references/` directory of their own: `agents/` is a flat namespace the Claude Code loader claims at any depth, so a companion skill is the supported way to give an agent reference material (issue #124). This file is PRELOADED into ticket-gate; the files under `references/` are NOT, and are read on demand. That is the difference #150 turned into a reduction: #109 moved material from the agent into this skill and reduced nothing, because both are preloaded, and the size guard reported a win it had not made. Moving the read-once artifacts one hop further takes 797 words out of every run. ## Wha