gate-check

Topics in the source

• gate-check
• When to load
• The gate contract
• How to use
• Audit every task
• Focus one task, compare a measured value
• Gotchas

Read a task's measurable acceptance gate from status/plan.md, compare a measured value to its threshold, and report PASS/FAIL with the numbers. CANARY: gate-check-loaded-2026-06-06-fb78d23e-e26f5d00ce664711 Load when a plan already carries a Gate column and the question is whether a finished task met it, with the measured number. execution writes the evidence; this skill verifies it, and review / ship run it. A gate is a measurable acceptance condition in the plan's task table, written with one of >= == !=: The evidence (measured value, command, commit SHA, environment provenance) lives in the plan's Evidence log table. Load references/gate-grammar.md when writing a gate the parser must read, defining the Evidence log columns, or diagnosing a gate reported "manual" or a task reported "grandfathered". The script defaults to status/plan.md; pass --input for any other path. Prints one line per task and a summary. Exit 0 when no gated task fails or lacks evidence, 1 otherwise. A manual (?) gate exits 0 once its evidence is recorded, so it still needs a human verdict before it counts as met. --strict also fails ungated tasks; without it they are grandfathered. Compares the measured 187

This is an excerpt. Refer to the complete source and its current requirements.