amoa-implementer-interview-protocol

To verify implementer readiness before PR creation, send standardized pre-task and post-task interviews to evaluate understanding, capability, and test evidence against acceptance criteria. This prevents premature or low-quality pull requests and reduces rework by producing explicit PROCEED, REVISE, or APPROVED decisions.

PR gating is the process of validating implementer readiness before pull request creation. It reduces escalation overhead by applying structured interviews to verify test evidence and acceptance criteria, routing immutable-requirement concerns to architects or managers via templated escalation messages rather than discovering issues during code review.

To escalate design concerns to an architect during module assignments, use templated escalation messages that route immutable-requirement issues away from the implementer. The process logs exception handling steps and updates issue labels according to AI Maestro orchestrator protocols to ensure proper tracking.

Yes, you can use structured interviews for automated handoff by evaluating implementer responses against acceptance criteria and generating explicit decisions. Once an APPROVED decision is produced, the workflow updates issue labels and generates handoff notifications to the Integrator according to AI Maestro orchestrator protocols.

The best way to structure pre-task and post-task interviews is to use operational documents that send standardized questions, collect structured responses, and evaluate readiness against acceptance criteria. This ensures messages, escalation templates, and handoff updates are logged correctly before producing PROCEED or REVISE decisions.

You should not use this interview protocol for PR gating when an issue requires immediate architectural decisions or involves immutable requirements that cannot be resolved at the implementer level. In these cases, direct escalation to the Manager or Architect is necessary instead of proceeding with the standard interview workflow.