gate-plan
Gate Plan — Gate Document Authoring
Produce a gate document for a queue item. The gate defines what must be proven before the work can be considered done. It is a production validation plan, not a checklist.
Input
The operator provides a Q-number (e.g., "Q4", "4"). This maps to a row in QUEUE.md.
Process
Step 0 — Bind the Input
The Q-number this gate plans against is not a parameter the skill body already holds: the harness appends it as an ARGUMENTS block after this skill's body. That trailing block is the ## Input above — read it as the Q-number to plan against, and resolve it against the matching QUEUE.md row and the frozen Q{n}-why.md in Step 1. This is the binding clause only — gate-plan's Step 1 (Resolve Context) already consumes that input, so no further consume-fix is needed, and gate-plan mints no Q-number; it reads one. The clause is here for defect-class consistency with the input-binding discipline applied across the chassis skills, not to repair a drift.