Verification As Context
Use when implementing or changing behavior, adding tests, choosing test level, or deciding what proof must ride with a change, to treat tests, docs, and CI as executable context that preserves product intent across fast agentic changes.
Multi Pass Planning
Use when a task is non-trivial, spans multiple files, affects architecture, requires tests or docs, or has unclear assumptions, to prevent premature coding by running Plan, Audit, Repair, Align, and Code as five distinct passes.
Manual Compaction Reset
Use when context is long, automatic compaction is likely, a session resumes after time away, direction changes, or the agent appears to be carrying stale assumptions, to perform a hard context reset by writing and reloading curated project context instead of relying on accumulated chat history.
Boundary Definition
Use when starting a feature, refactor, integration, API change, or state-machine change, before writing code, to force explicit interfaces, inputs, outputs, contracts, invariants, ownership, non-goals, and failure modes.
Collaboration Checkpoint
Use when repeated fixes fail, the same error recurs, progress stalls, the user says the agent is missing something, or the agent has high uncertainty, to break debugging death spirals and trigger humility by pausing code churn, summarizing attempts, and surfacing the user's system intuition.