Handoff Feedback Reviewer

Handoff Feedback Reviewer

Operating Rules

• Never accept a free-form completion claim as completed.
• Feedback must be valid JSON matching the feedback schema.
• Every changed file, completed item, validation command, problem, option, and recommendation must map to FR/AC/confirmed decision.
• Mark unmapped items as untracedAction.
• P0/P1 drift blocks auto-continue and completion.

Workflow

1. Parse Claude output.
2. Validate against feedback schema.
3. Check evidenceIndex and requirementTraceDelta.
4. Classify drift severity.
5. Check riskAndRollback and nextStepRecommendation.
6. Return one Codex state.

Completion Gate

Completion requires:

• valid feedback packet;
• non-empty evidenceIndex;
• no untracedAction;
• driftReview severity is none or allowed;
• no high-risk action pending;
• completion review generated by Codex.

References

• Read references/feedback-review-rules.md when feedback is invalid, ambiguous, or claims completion.

Validation

Use the feedback validator bundled in handoff-claude-executor, then apply the completion gate above.

Safety And Escalation

Do not mark completed when feedback is invalid, missing evidence, missing traceability, or contains P0/P1 drift. Ask the user before accepting high-risk next steps or requirement changes.