goal-quench

# goal-quench — /goal with Token Budget + Quality Gate **Availability of `/goal` is unresolved** — treat it the way `CLAUDE.md` treats `/deep-research`: use the built-in **if present**, and do not assert it is absent either. Everything below applies to whatever autonomous-run command this environment actually has; goal-quench is the wrapper, not the runner. Probe before relying on it (`/help`, or the skill/command list), and say which you found. `/goal` is understood to run until a cheap per-turn judge (reported as Haiku) says "done" — that is **second-hand, not verified here**, so treat it as the assumption goal-quench is designed against rather than as a fact about the implementation. What matters for this skill holds either way: a completion judge is not a quality judge, and without a budget ceiling a session can exhaust tokens silently. goal-quench adds three things such a runner does not itself provide: 1. **Pre-run**: token-budget-gate estimate — know the cost before committing 2. **Mid-run**: budget threshold awareness — signal before exhaustion (instructional; not mechanically enforced) 3. **Post-run**: pipeline-conductor — verify quality before accepting "done" The evaluator principle: the runner's own per-turn judge decides completion (every turn, cheap). pipeline-conductor judges quality (once at the end, structured). Separating the two closes the self-evaluation bias that a single evaluator cannot avoid — the principle holds whatever model that per-turn judge ...