feat: add pre-task-calibration — mechanical pre-action verification#1422
Open
YuhaoLin2005 wants to merge 8 commits into
Open
feat: add pre-task-calibration — mechanical pre-action verification#1422YuhaoLin2005 wants to merge 8 commits into
YuhaoLin2005 wants to merge 8 commits into
Conversation
…rences/patterns.md + evals/evals.json
…ead See-Also, clarify Hard Constraints, expand Verification
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A PreToolUse hook that enforces three mandatory checks before any Edit/Write operation: concept review, input consistency, and verification planning. Any check fails → exit 2, tool call blocked.
Why
The most expensive mistakes happen before the first keystroke — editing in the wrong direction. Pre-task calibration catches these at the only moment prevention is cheaper than correction.
How It Works
PreToolUse (Edit/Write/Bash) → Q1: Approach validated? → Q2: Inputs consistent? → Q3: Verification planned? → All three pass → allow.
Integration
Module A of a composable quality pipeline. Works standalone. Complements:
Each module is independent — adopt any, all, or none. Together they form defense in depth across the full session lifecycle.
Evidence
50+ session production use. Causal experiment (n=30, p=0.0092): config rules measurably change agent behavior. Mechanical enforcement via exit codes is more reliable than aspirational prompts.