amoa-implementer-interview-protocol

Use when verifying implementer readiness. Trigger with interview or PR approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-implementer-interview-protocol is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when verifying implementer readiness. Trigger with interview or PR approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-implementer-interview-protocol should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-implementer-interview-protocol/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-implementer-interview-protocol/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-implementer-interview-protocol/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-implementer-interview-protocol Compares

Feature / Agentamoa-implementer-interview-protocolStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when verifying implementer readiness. Trigger with interview or PR approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Implementer Interview Protocol

## Overview

Interview implementers pre/post task to verify readiness and quality before PR creation.

## Prerequisites

AGENT_OPERATIONS.md, amoa-label-taxonomy, amoa-messaging-templates.

## Output

Interview decision (PROCEED/APPROVED/REVISE), handoff doc, and issue label update.

## Instructions

1. Identify implementer and issue. Send Pre-Task Interview via `agent-messaging`
   - Questions: [interview-templates.md](./references/interview-templates.md)
   <!-- TOC: Pre-Task Interview Questions | Post-Task Interview Questions -->
   - Escalation: [escalation-messages.md](./references/escalation-messages.md)
   <!-- TOC: REVISE Message | PROCEED Message -->
2. Evaluate responses; send PROCEED or REVISE
3. After execution, send Post-Task Interview. All pass → APPROVED, major → REVISE
4. On APPROVED, create PR, set `status:ai-review`, notify Integrator per [handoff-and-output.md](./references/handoff-and-output.md)
   <!-- TOC: Output Types | Handoff to Integrator -->

Copy this checklist and track your progress:

- [ ] Send Pre-Task Interview and evaluate
- [ ] Send PROCEED or REVISE
- [ ] Send Post-Task Interview and evaluate
- [ ] On APPROVED, execute handoff

Steps: [interview-workflow-steps.md](./references/interview-workflow-steps.md)
<!-- TOC: Pre-Task Interview Checklist | Post-Task Interview Checklist | Pre-Task Interview Steps | Post-Task Interview Steps -->

## Error Handling

See: [exception-handling.md](./references/exception-handling.md)
<!-- TOC: Implementer Disagrees with Requirements | Architect Recommends Design Change | User Approves Requirement Change | Implementer Never Acknowledges | Implementer Misunderstands Task | Implementer Has Design Concerns | Implementer Reports Incomplete Work | Tests Fail in Post-Task Interview | Implementer Creates PR Before Approval -->

## Examples

See [examples.md](./references/examples.md)
<!-- TOC: Example 1: Send Pre-Task Interview Questions | Example 2: Escalate Design Concern to Architect | Example 3: Send PROCEED After Satisfactory Interview | Example 4: Send Post-Task Verification Questions | Example 5: Send APPROVED and Handoff to Integrator -->

**Input:** Issue #42 assigned to `libs-svg-svgbbox`. **Output:** Pre-task → PROCEED → post-task → APPROVED → Integrator notified.

## Resources

- [interview-templates.md](./references/interview-templates.md)
  - Pre-Task Interview Questions
  - Pre-Task Interview: {TASK_ID}
  - Post-Task Interview Questions
  - Post-Task Interview: {TASK_ID}
  - ...
- [escalation-messages.md](./references/escalation-messages.md)
  - Design Issues → Architect
  - Immutable Requirement Issues → Manager → User
  - PROCEED Message
  - PROCEED: {TASK_ID}
  - ...
- [exception-handling.md](./references/exception-handling.md)
  - 1. Implementer Disagrees with Requirements
  - 2. Architect Recommends Design Change
  - 3. User Approves Requirement Change
  - 4. Implementer Never Acknowledges
  - ...
- [examples.md](./references/examples.md)
  - Example 1: Send Pre-Task Interview Questions
  - Example 2: Escalate Design Concern to Architect
  - Example 3: Send PROCEED After Satisfactory Interview
  - Example 4: Send Post-Task Verification Questions
  - ...
- [interview-workflow-steps.md](./references/interview-workflow-steps.md)
  - Pre-Task Interview Checklist
  - Post-Task Interview Checklist
  - Pre-Task Interview Steps
  - Post-Task Interview Steps
- [handoff-and-output.md](./references/handoff-and-output.md)
  - Handoff to Integrator
    - When PR is Created
    - Responsibility Transfer
  - Output Types

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-two-phase-mode

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-task-distribution

7
from Emasoft/ai-maestro-orchestrator-agent

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-remote-agent-coordinator

7
from Emasoft/ai-maestro-orchestrator-agent

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent