minhtran3124/agent-harness/intent-review

Intent Review

This is the intent oracle: it is neither a runtime-bug hunt nor a style review. Run it standalone with a supplied intent, or after correctness review in SDD before finishing a branch.

Establish a blind oracle

1. Read ### Intent from specs/<slug>/SUMMARY.md; it is the verbatim primary oracle.
2. Optionally read design success criteria and PLAN §3 SC rows only as secondary checks. A missing

SUMMARY intent and design intent is a STOP: ask the user instead of reconstructing intent.

1. If a secondary oracle conflicts with verbatim intent, verbatim wins and the conflict is drift.
2. Determine BASE..HEAD (task-start to HEAD in SDD, merge-base to HEAD for a branch, or an

explicit range). Give the reviewer the oracle, diff, touched files, SC table, and SUMMARY Verify table—but never PLAN.md prose or research-brief.md.

When SDD supplies REVIEW_PACKAGE_PATH, the reviewer reads that mechanical BASE..HEAD package first instead of rebuilding the same diff. The package carries no intent oracle; do not use it to read PLAN prose or research material. Standalone calls without a package retain explicit-range construction.

Dispatch intent-reviewer-prompt.md in fresh context. Every finding must quote the intent sentence it evaluates.

Route findings

• gap: a requested outcome—or a promised SC with no mapped passing Verify row—is missing.

Fix if unambiguous and in scope; otherwise escalate.

• drift: implementation differs from requested behavior. Record equivalent drift as advisory;

route material behavior changes like gaps.

• excess: unrequested behavior or public surface. Report only: do not remove shipped behavior

without human approval.

Before any fix routing, read `rules/auto-correct-scope.md`. Put ambiguous gaps/drift and intent conflicts in ESCALATIONS.md; put advisory drift, excess, and deferred findings in SUMMARY.md under ### Intent Findings. A finding must be fixed with its commit SHA or durably recorded before handoff; otherwise completion is blocked.

The plan/spec reviewer is plan-oriented and correctness-review is runtime-oriented. Keep this oracle separate and plan-blind; it is the check for “implemented correctly, but not what was asked.”