From emasoft-orchestrator-agent
Trigger with module management tasks. Use when managing modules during Orchestration Phase (add, modify, remove, prioritize, reassign). Every module maps 1:1 to GitHub Issue.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-orchestrator-agentThis skill uses the workspace's default tool permissions.
This skill teaches orchestrators how to dynamically manage modules during the Orchestration Phase.
README.mdreferences/github-issue-sync.mdreferences/module-creation.mdreferences/module-modification.mdreferences/module-prioritization.mdreferences/module-reassignment.mdreferences/module-removal-rules.mdreferences/op-add-module-midorchestration.mdreferences/op-change-module-priority.mdreferences/op-modify-module-specs.mdreferences/op-reassign-module-agent.mdreferences/op-remove-pending-module.mdreferences/op-sync-module-github-issue.mdreferences/troubleshooting.mdscripts/__pycache__/github_sync.cpython-314.pycscripts/__pycache__/module_operations.cpython-314.pycscripts/github_sync.pyscripts/module_operations.pyManages modules in AI Maestro Orchestration Phase by handling add, modify, reassign requests via GitHub Issues with gh CLI. Delegates to sub-skills for CRUD and sync.
Orchestrates multi-agent parallel execution for complex tasks like features, refactoring, testing, reviews, and documentation using cc-mirror tracking and TodoWrite visibility.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Share bugs, ideas, or general feedback.
This skill teaches orchestrators how to dynamically manage modules during the Orchestration Phase.
design/state/exec-phase.md exists Modules are the atomic units of work in EOA orchestration. Each module represents one feature, component, or deliverable that an agent will implement.CRITICAL RULE: Every module is tied 1:1 to a GitHub Issue. When you add a module, an issue is created. When you remove a module, the issue is closed. When you modify a module, the issue is updated. This linkage ensures traceability and transparency.
design/state/exec-phase.md| Output Type | Format | Location |
|---|---|---|
| Module state update | YAML | design/state/exec-phase.md |
| GitHub Issue created/updated | Issue number | GitHub repository |
| Agent notification | AI Maestro message | Agent inbox |
| Command success/failure | Status message | Console output |
| Command | Purpose | When to Use |
|---|---|---|
/add-module | Add new module | User requests new feature |
/modify-module | Change module specs | Criteria or priority change |
/remove-module | Delete pending module | Module cancelled |
/prioritize-module | Change priority level | Urgency changed |
/reassign-module | Transfer to different agent | Agent stuck or unavailable |
/add-module with name and criteriaRead: module-creation.md
/modify-module with new specsRead: module-modification.md
pending/remove-module with module IDRead: module-removal-rules.md
/prioritize-module with new levelRead: module-prioritization.md
/reassign-module with new agent IDRead: module-reassignment.md
Every module in EOA orchestration has a corresponding GitHub Issue. This relationship is fundamental and cannot be bypassed.
| Reason | Benefit |
|---|---|
| Traceability | All work is tracked in GitHub |
| Transparency | Stakeholders see progress |
| Integration | PRs link to issues |
| History | Changes documented |
| Accountability | Assignment visible |
| Module Event | GitHub Issue Action |
|---|---|
| Module added | Issue created with labels |
| Module modified | Issue body/labels updated |
| Module removed | Issue closed with wontfix |
| Priority changed | Priority label updated |
| Agent assigned | Issue assigned to developer |
| Module completed | Issue closed with linked PR |
Read: github-issue-sync.md
Usage: /add-module "<NAME>" --criteria "<TEXT>" [--priority LEVEL]
| Argument | Required | Description |
|---|---|---|
| NAME | Yes | Display name for the module |
| --criteria | Yes | Acceptance criteria text |
| --priority | No | critical, high, medium, low (default: medium) |
What Happens:
Example:
/add-module "Two-Factor Auth" --criteria "Support TOTP and SMS" --priority critical
Usage: /modify-module <MODULE_ID> [--name NAME] [--criteria TEXT] [--priority LEVEL]
| Argument | Required | Description |
|---|---|---|
| MODULE_ID | Yes | ID of module to modify |
| --name | No | New display name |
| --criteria | No | New acceptance criteria |
| --priority | No | New priority level |
Restrictions:
pending modules: All fields modifiablein-progress modules: Modifiable with agent notificationcomplete modules: Cannot modifyExample:
/modify-module auth-core --criteria "Support JWT with 24h expiry" --priority high
Usage: /remove-module <MODULE_ID> [--force]
| Argument | Required | Description |
|---|---|---|
| MODULE_ID | Yes | ID of module to remove |
| --force | No | Skip confirmation |
Restrictions:
pending modules can be removedin-progress modules cannot be removedcomplete modules cannot be removedExample:
/remove-module oauth-facebook
Usage: /prioritize-module <MODULE_ID> --priority <LEVEL>
| Argument | Required | Description |
|---|---|---|
| MODULE_ID | Yes | ID of module |
| --priority | Yes | critical, high, medium, low |
Example:
/prioritize-module auth-core --priority critical
Usage: /reassign-module <MODULE_ID> --to <AGENT_ID>
| Argument | Required | Description |
|---|---|---|
| MODULE_ID | Yes | ID of module to reassign |
| --to | Yes | ID of new agent |
What Happens:
Example:
/reassign-module auth-core --to implementer-2
Module management commands modify the orchestration state file at design/state/exec-phase.md.
modules_status:
- id: "auth-core" # Kebab-case identifier
name: "Core Authentication" # Display name
status: "pending" # pending|assigned|in-progress|complete
assigned_to: null # Agent ID or null
github_issue: "#42" # Linked issue number
pr: null # Linked PR when complete
verification_loops: 0 # Number of review cycles
acceptance_criteria: "Support JWT and session tokens"
priority: "high" # critical|high|medium|low
active_assignments:
- agent: "implementer-1"
agent_type: "ai"
module: "auth-core"
github_issue: "#42"
task_uuid: "task-abc123def456"
status: "pending_verification"
instruction_verification:
status: "awaiting_repetition"
repetition_received: false
repetition_correct: false
questions_asked: 0
questions_answered: 0
authorized_at: null
# User requests two-factor authentication
/add-module "Two-Factor Auth" --criteria "Support TOTP and SMS" --priority critical
# System automatically creates GitHub Issue #43
# Module appears in pending queue with status: pending
# Agent implementer-1 is blocked on auth-core
# Request progress report first
/check-agents --agent implementer-1
# Reassign to implementer-2
/reassign-module auth-core --to implementer-2
# Old agent notified to stop
# New agent receives full assignment with Instruction Verification Protocol reset
| Problem | Likely Cause | Solution |
|---|---|---|
| Module not found | Wrong ID used | Use /orchestration-status to see actual IDs |
| Cannot remove module | Status not pending | Modify scope instead of removing |
| GitHub Issue not created | gh CLI not authenticated | Run gh auth login |
| Agent not notified | AI Maestro not running | Verify AI Maestro AMP messaging is running using the agent-messaging skill health check |
| Priority not updating | Issue labels mismatch | Manually update GitHub Issue |
For detailed troubleshooting: troubleshooting.md
Location: scripts/module_operations.py
Provides programmatic access to all module operations:
# Add module
python3 scripts/module_operations.py add "Module Name" --criteria "Criteria"
# Modify module
python3 scripts/module_operations.py modify module-id --priority critical
# Remove module
python3 scripts/module_operations.py remove module-id
# List modules
python3 scripts/module_operations.py list
# Validate module state
python3 scripts/module_operations.py validate
Location: scripts/github_sync.py
Synchronizes module state with GitHub Issues:
# Sync all modules to GitHub
python3 scripts/github_sync.py sync-all
# Sync specific module
python3 scripts/github_sync.py sync module-id
# Verify sync status
python3 scripts/github_sync.py verify
| Reference | Contents |
|---|---|
| module-creation.md | Add-module workflow, validation, examples |
| module-modification.md | Modify specs, notifications, restrictions |
| module-removal-rules.md | Removal conditions, cleanup, alternatives |
| module-prioritization.md | Priority levels, effects, label updates |
| module-reassignment.md | Transfer workflow, notifications, reset |
| github-issue-sync.md | Issue creation, labels, sync protocol |
| troubleshooting.md | Error recovery, force operations |
| Command | Purpose |
|---|---|
/orchestration-status | View all modules and assignments |
/assign-module | Initial assignment to agent |
/check-agents | Monitor agent progress |
/register-agent | Register new agents |
| Action | Command | Restrictions |
|---|---|---|
| Add module | /add-module | None |
| Modify specs | /modify-module | Cannot modify complete |
| Remove module | /remove-module | Pending only |
| Change priority | /prioritize-module | None |
| Reassign agent | /reassign-module | Cannot reassign complete |
Key Principles:
Copy this checklist and track your progress: