amoa-module-lifecycle

name	amoa-module-lifecycle
description	Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent
license	Apache-2.0
compatibility	Python 3.8+, PyYAML, gh CLI, AI Maestro.
metadata	{"author":"Emasoft","version":"1.0.0"}
user-invocable	false
context	fork
agent	amoa-main

Module Lifecycle Commands Skill

Overview

Core CRUD operations for modules during Orchestration Phase. Each module maps 1:1 to a GitHub Issue.

Prerequisites

Orchestration Phase active, gh CLI authenticated, AI Maestro running.

Output

Module ID, Issue number, state update, and agent notification status.

Instructions

1. Identify action: add, modify, remove, prioritize, or reassign
2. Run the command and verify state update in design/state/exec-phase.md
3. Confirm GitHub Issue sync and notify agents via AI Maestro

Copy this checklist and track your progress:

• Identify action and verify prerequisites
• Execute command and verify state update
• Confirm Issue sync and notify agents

Commands: /add-module, /modify-module, /remove-module, /prioritize-module, /reassign-module. Syntax: command-details.md

/add-module -- module-creation.md

/modify-module -- module-modification.md

/remove-module (pending only) -- module-removal-rules.md

/prioritize-module -- module-prioritization.md

/reassign-module -- module-reassignment.md

Examples

Input: /add-module "Two-Factor Auth" --criteria "Support TOTP and SMS" --priority critical Output: Module two-factor-auth created, Issue #43 opened, pending

Input: /reassign-module auth-core --to implementer-2 Output: Old agent stopped, new agent assigned, verification reset

Error Handling

Module not found: run /orchestration-status. Cannot remove: status not pending. Agent not notified: check AI Maestro AMP.

Resources

See reference files above for complete command syntax and details.