harness

Break seed AC into atomic layer-aware tasks BEFORE /run. USE WHENEVER implementation spans multiple files or layers. Prevents mega-prompts; each unit is independently implementable and testable.

Run 3-stage verification (Mechanical gates → Semantic AC compliance → Judgment quality) after /run. ALWAYS run before committing. Blocks at Stage 1 failures — no Stage 2 until gates pass.

Evolve the system when /evaluate fails. Runs Wonder → Reflect → Re-seed cycle with fan-out multi-perspective analysis (Contrarian + Simplifier + Researcher). Stops at convergence (ontology similarity ≥ 0.95).

Interactive installation wizard for AI Harness Template. Guides through version, track, permissions, gates, and more via step-by-step questions.

START HERE for ANY new feature or unclear requirement. Socratic interview that surfaces hidden assumptions before a single line of code is written. Measures 4D ambiguity score — blocks progress until score ≤ 0.2.

USE THIS WHEN symptoms keep recurring, layer boundaries blur, or changes ripple unexpectedly. ALWAYS invoke for structural diagnosis during /unstuck or major refactors. Finds root causes in design, not symptoms. Names tradeoffs explicitly.

USE THIS WHEN the team reaches quick consensus, before committing to a major design decision, or during /evolve and /unstuck. Challenges assumptions with "what if we're wrong?" scenarios. Always proposes at least one alternative.

USE THIS WHEN verifying implementation against a seed spec, running gates, or assessing AC compliance. ALWAYS invoke during /evaluate. Never fixes — only judges Pass/Fail with file:line evidence. Runs 3-stage verification (Mechanical → Semantic → Judgment).

USE THIS WHEN the official path is blocked, a deadline looms, or a temporary workaround is acceptable. ALWAYS invoke during /unstuck when standard approaches fail. Finds safe bypasses (monkey-patch, polyfill, shim) with explicit expiry dates.

USE PROACTIVELY whenever the user describes a new feature, vague requirement, or unclear goal. ALWAYS run BEFORE writing code or creating a seed spec. Asks Socratic questions to surface hidden assumptions. Never writes code or gives answers — only questions.