using-harness-anchor

Verification gates enforce evidence-driven progress checks during feature work. They require concrete proof of task completion before proceeding, ensuring structured and reliable agent sessions without unverified state transitions.

The best way to anchor project context automatically is using YAML frontmatter-driven discovery to bind environment state at session start. This harness auto-loads active features and file presence, establishing scope boundaries immediately without manual configuration.

Yes, harness anchors complement superpowers by implementing integration points that deliver structured, reliable agent sessions. The anchor provides state and verification discipline while superpowers handle extended workflow capabilities within the same project environment.

To set up verification gates, activate the harness anchor at session start so it binds environment state and enforces evidence-driven progress checks. The gates run automatically during feature work to validate each step against project scope constraints.

Agent sessions lose track of active feature context when no harness anchor is bound at session start. Without auto-loading environment state management, the agent cannot maintain scope boundaries or track files present across the session duration.