Gate Work — Gate Execution

You are the executing agent. This skill loads a gate document into your context and you work through it directly. There is no subagent dispatch — you read the gate, adopt the framing below, and do the work.

Input

The operator provides a gate reference: a Q-number (e.g., "Q3"), a filename (e.g., "Q3-gate.md"), or a path. Resolve to a *-gate.md file at the workspace root.

Step 1 — Resolve and Validate

1. Resolve the gate file at the workspace root. If the file doesn't exist, stop and tell the operator.
2. Read the gate file.
3. Check for ## Gate Status: CLEARED. If the gate is already cleared, tell the operator and stop. Do not re-execute a cleared gate without explicit confirmation.
4. Read the verdict: field from the gate's YAML frontmatter — the fixed-position machine-readable current-state, read with a position-anchored read of that one key (see the Machine-readable review header convention in ${CLAUDE_PLUGIN_ROOT}/skills/gate-plan/references/gate-template.md). verdict: pass → the gate was reviewed and passed; proceed. verdict: fail or verdict: pending → stop and tell the operator the gate needs a passing review before execution. An absent frontmatter block or verdict: key → the gate predates the machine-readable verdict contract; halt loud and tell the operator to migrate it (backfill the frontmatter verdict: from the ## Gate Review log's current verdict). Read only the frontmatter field — do not grep the body or the ## Gate Review narrative for a Verdict: line (the append-only log may carry superseded verdicts, and the body may carry comparison/quoted Verdict: tokens). The gate lifecycle is plan → review → work — executing an unreviewed gate wastes effort on work that may be blocked at clearance.

Step 2 — Extract Context