amoa-module-management
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Best use case
amoa-module-management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Teams using amoa-module-management 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/amoa-module-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How amoa-module-management Compares
| Feature / Agent | amoa-module-management | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign 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
# Module Management Commands Skill ## Overview Manages modules during Orchestration Phase. Each module maps 1:1 to a GitHub Issue. This skill has been split into focused sub-skills: - **amoa-module-lifecycle** -- Core CRUD: add, modify, remove, prioritize, reassign modules - **amoa-module-sync** -- GitHub Issue sync, troubleshooting, usage examples ## Prerequisites Orchestration Phase active, gh CLI authenticated, AI Maestro running. ## Output Module ID, Issue number, state update, and agent notification status. ## Instructions 1. For module CRUD operations, see skill `amoa-module-lifecycle` 2. For GitHub Issue sync and troubleshooting, see skill `amoa-module-sync` Copy this checklist and track your progress: - [ ] Identify action and verify prerequisites - [ ] Execute command via the appropriate sub-skill - [ ] Confirm Issue sync and notify agents ## Examples **Input:** `/add-module "Two-Factor Auth" --criteria "Support TOTP and SMS" --priority critical` **Output:** Module `two-factor-auth` created, Issue #43 opened, pending ## Error Handling Module not found: run `/orchestration-status`. Cannot remove: status not pending. ## Resources - See skill `amoa-module-lifecycle` for command details and module CRUD - See skill `amoa-module-sync` for GitHub sync and troubleshooting
Related Skills
amoa-verification-patterns
Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-two-phase-mode
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
Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-remote-agent-coordinator
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
Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-plan-phase
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
Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-orchestration-loop
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
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-lifecycle
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
Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-label-taxonomy
Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent