Your Agent Pipeline's Review Gate Should Be Code, Not a Prompt Convention

说明与用途

将 ZOdyssey 的审查门从提示约定迁移到代码，实现可靠的审查门，防止回归并确保计划完整性。

问题

Agent pipelines often rely on prompt conventions to enforce review gates, which can be bypassed and lead to regressions such as accidental deletion of critical gates.

结果

By moving the review gate from a prompt to code, ZOdyssey prevents accidental gate removal, enforces plan integrity, and ensures that product code changes only occur after a verified OKAY verdict.

工作流

• 1. Define plan in .zcode/plans/<slug>.md and run scripts/parse-plan.mjs to lint it.
• 2. Execute the REVIEW phase via momus, which produces a verdict (OKAY or REJECT) and records a plan SHA256.
• 3. The PreToolUse hook (skills/odyssey/hooks/pre-tool.mjs) checks state.review.verdict; if not OKAY, it blocks any product code edits.
• 4. If the plan is edited after an OKAY verdict, the hook re‑hashes the plan and compares it to the bound SHA; a mismatch blocks the edit and requires re‑review.
• 5. Upon successful review, executors run the EXECUTE phase, limited to plan‑specified files and capped dispatches.
• 6. Verification runs acceptance criteria and records evidence; record‑todo refuses completion without passing records.

证据

The Bash gate has been silently deleted TWICE.

来源

The review gate itself, pre-tool.mjs:876-884

来源