amoa-module-management

Manage modules and synchronize them with GitHub Issues via gh CLI.

13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-module-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amoa-module-management
Source: https://github.com/Emasoft/ai-maestro-orchestrator-agent/tree/main/skills/amoa-module-management
Command: npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-module-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manage dynamic project modules during the Orchestration Phase and eliminate manual coordination by ensuring every module maps 1:1 to a GitHub Issue, keeping state, labels, and assignments synchronized across systems and agents.

Core Features & Use Cases

  • Module CRUD: Add, modify, remove, and prioritize modules with automatic state updates.
  • GitHub Issue Sync: Create and update issue titles, bodies, labels, and assignees via the gh CLI to reflect module state.
  • Assignment & Reassignment: Transfer modules between AI or human implementers with STOP notifications and verification resets.
  • Verification & Recovery: Instruction verification protocol, retry/sync scripts, and troubleshooting guidance for desyncs and failures.
  • Use case: Add a new feature mid-orchestration, automatically create its issue, notify agents, and ensure the stop-hook and orchestration state reflect the change.

Quick Start

Request the orchestrator to add a module by providing the module name, acceptance criteria, and optional priority to create the module and its linked GitHub Issue.

Frequently Asked Questions about amoa-module-management

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

FAQPage Schema
How do I keep GitHub issues in sync with project modules during multi-agent orchestration?

Synchronizing GitHub issues with project modules uses an orchestration state file and the gh CLI to map each module 1:1 to an issue. It automatically updates titles, bodies, labels, and assignees to reflect changes made during the orchestration phase.

How do I reassign a module between AI and human implementers without losing orchestration state?

Reassigning modules between implementers triggers STOP notifications and verification resets. The orchestration state file and linked GitHub issue are updated simultaneously to ensure the new assignee receives the correct, current module context without state desync.

Can I add a new feature module mid-orchestration and automatically generate its GitHub issue?

Adding a feature module mid-orchestration automatically creates a linked GitHub issue with the provided name, acceptance criteria, and priority. The local orchestration state and stop-hooks are immediately updated to reflect the new module.

What is the best way to handle desyncs between local orchestration state and GitHub issues?

Handling desyncs involves an instruction verification protocol and retry scripts. These tools troubleshoot failures by re-attempting the gh CLI sync commands to restore a correct 1:1 mapping between your modules and GitHub issues.

Do I need the gh CLI installed to manage modules and sync issues in multi-agent workflows?

The gh CLI is required to create and update GitHub issue titles, bodies, labels, and assignees. The orchestration state file relies on it to execute the actual synchronization between your local modules and the GitHub repository.

How does module prioritization work during the orchestration phase?

Module prioritization during the orchestration phase updates the local state file and the linked GitHub issue's labels to reflect the new priority. This ensures AI and human implementers process modules in the correct sequence.