eoa-implementer-interview-protocol

Validate implementer understanding through pre-task and post-task interviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Emasoft/emasoft-orchestrator-agent --skill eoa-implementer-interview-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eoa-implementer-interview-protocol
Source: https://github.com/Emasoft/emasoft-orchestrator-agent/tree/main/skills/eoa-implementer-interview-protocol
Command: npx skills add https://github.com/Emasoft/emasoft-orchestrator-agent --skill eoa-implementer-interview-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured protocol to verify that an implementer clearly understands a task before starting work, ensuring alignment, reducing rework, and enabling safe handoffs to integration.

Core Features & Use Cases

  • Pre-task and Post-task interview workflows to validate understanding and track decisions.
  • Escalation and handoff templates to involve architects, managers, and integrators.
  • Automated logging of interview outcomes and progression to PROCEED/APPROVED/REVISE.

Quick Start

Initiate a Pre-task Interview by sending the five-question template to the implementer via AI Maestro. Await responses, evaluate, and decide PROCEED/APPROVE/REVISE. Prepare post-task verification questions after [DONE] reported.

Frequently Asked Questions about eoa-implementer-interview-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate implementer understanding before task execution?▼

You validate implementer understanding by initiating a pre-task interview with a five-question template via AI Maestro, evaluating the responses, and deciding whether to PROCEED, APPROVE, or REVISE the task.

What is the best way to structure an escalation and handoff to an integrator after task completion?▼

The best way to structure an escalation and handoff is by using post-task interview workflows and dedicated templates to involve architects, managers, and integrators, ensuring safe progression and documentation updates.

How does the post-task interview process work after a task is reported as done?▼

After a task is reported as [DONE], the post-task interview process works by preparing verification questions to track decisions, validate outcomes, and gate the final handoff to the integrator.

When do I need to use PROCEED, APPROVED, or REVISE messages in a pre-task interview?▼

You need to use PROCEED, APPROVED, or REVISE messages during pre-task interviews to enforce gating, controlling whether the implementer can start work or must revise their understanding based on the evaluation.

Can I use this interview protocol to involve architects and managers in task approvals?▼

Yes, you can use this protocol to involve architects and managers in task approvals through built-in escalation workflows and handoff templates designed to align stakeholders before integration.

Why does an implementer interview protocol help reduce rework in software engineering?▼

An implementer interview protocol reduces rework by verifying task alignment and clearly documenting decisions before execution begins, ensuring all stakeholders share a precise understanding of the requirements.