Show the project's current harness maturity phase, the artifact metrics behind it, and which harness capabilities are unlocked. Use at session start or when deciding whether to adopt heavier harness practices (evaluator, golden regression, etc.).
Dispatch the skeptical evaluator subagent to score the current change against the project rubric (Generator/Evaluator separation). Use before declaring a coding task done, or when the Stop gate recommends it.
Initialize harness-kit in the current project. Detects or asks the project type (godot | web | custom) and language (en | zh), scaffolds .harness/config.json + rubric + plan/docs skeleton + a ToC-style CLAUDE.md when the project has none, and enables the git pre-commit gate; then analyzes the codebase to fill in the…
Start the Plan→Build→Verify→Done workflow for a non-trivial change. Enters plan mode seeded with the project's plan template; on approval, the ExitPlanMode hook persists the plan into the configured plan directory. Use before any change larger than 20 lines or touching planned code paths.
Analyze the harness's own session trace for failure patterns — verify pass/fail rate, session imbalance, and high-churn (doom-loop) files. Use periodically to decide how to tune the harness itself (thresholds, gates, reasoning budget).
Run the project's harness verification gates (the config-driven harness-verify orchestrator) and report per-gate pass/fail. The manual counterpart to the automatic Stop-hook gate. Use to check work mid-task before declaring done.