gate git:20260907.2c692edA

Immutable. This exact content never changes and is served at /api/v1/blob/c7996a706af16993.

---
name: gate
description: Use when a Kraft Lite chain is blocked at a gate - presents what the human must decide on, then records their approval or rejection.
---

# Gates

A gate is a decision that belongs to a human. You present, they decide.

Run `python3 "$CLAUDE_PLUGIN_ROOT/kl.py" state` for the gate name, then show them
what the gate is actually about - the spec, the plan, the diff, the findings. A
gate answered without the artefact in front of the person is a gate that has
stopped meaning anything.

Then, on their answer:

    python3 "$CLAUDE_PLUGIN_ROOT/kl.py" approve
    python3 "$CLAUDE_PLUGIN_ROOT/kl.py" reject --note "<their reason>"

`--note` is required. A rejection with no reason strands whoever picks the work
up next, including you after a compaction.

After an approve, invoke the `next` skill. After a reject, invoke `next` too: the
node reopens and its note leads the retry.

Never call `approve` because the answer seemed obvious. If the human has not
answered, the gate is not answered.

`$CLAUDE_PLUGIN_ROOT` is set when this loads as a plugin. If it is unset, `kl.py`
is two directories above this file - use that path instead of an empty one.