From ai-maestro-orchestrator-agent
Modifies module specifications (name, criteria, priority) by MODULE_ID during orchestration. Updates state file, GitHub issue, notifies assigned agent if in-progress.
How this command is triggered — by the user, by Claude, or both
Slash command
/ai-maestro-orchestrator-agent:amoa-modify-module <MODULE_ID> [--name NAME] [--criteria TEXT] [--priority LEVEL]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Modify Module Command Change the specifications of a module during Orchestration Phase. If module is assigned, notifies the assigned agent. ## Usage ## Arguments | Argument | Required | Description | |----------|----------|-------------| | `MODULE_ID` | Yes | ID of the module to modify | | `--name` | No | New display name | | `--criteria` | No | New acceptance criteria | | `--priority` | No | New priority level | ## What This Command Does 1. **Updates Module Specifications** - Changes requested fields - Updates state file 2. **Updates GitHub Issue** - Syncs changes to li...
Change the specifications of a module during Orchestration Phase. If module is assigned, notifies the assigned agent.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/amoa_modify_module.py" modify $ARGUMENTS
| Argument | Required | Description |
|---|---|---|
MODULE_ID | Yes | ID of the module to modify |
--name | No | New display name |
--criteria | No | New acceptance criteria |
--priority | No | New priority level |
Updates Module Specifications
Updates GitHub Issue
Notifies Assigned Agent (if assigned)
agent-messaging skill| Module Status | Can Modify? |
|---|---|
pending | ✓ All fields |
in_progress | ✓ With notification |
complete | ✗ Cannot modify |
When modifying an in-progress module, the assigned agent receives:
Subject: [UPDATE] Module: {module_name} - Spec Change
The specifications for your assigned module have been updated:
**Changes:**
- Criteria: {new_criteria}
- Priority: {new_priority}
Please acknowledge this update and adjust your implementation accordingly.
If this significantly impacts your current work, report the impact immediately.
# Add criteria to existing module
/modify-module auth-core --criteria "Support JWT with 24h expiry"
# Change priority
/modify-module oauth-google --priority critical
# Change name
/modify-module auth-2fa --name "Multi-Factor Authentication"
# Multiple changes
/modify-module password-reset --criteria "Include OTP option" --priority high
The module entry is updated with new values:
modules_status:
- id: "auth-core"
name: "Core Authentication"
status: "in_progress"
acceptance_criteria: "Support JWT with 24h expiry" # Updated
priority: "critical" # Updated
# ... other fields unchanged
/orchestration-status - View module details/add-module - Add new module/remove-module - Remove pending modulenpx claudepluginhub emasoft/ai-maestro-orchestrator-agent/modifyApplies targeted modifications to the current workflow phase without restarting, optionally with light brainstorming, updates deliverables, and shows updated approval gate.
/issue-updateUpdates existing tickets/issues with status changes, comments, assignees, labels, priority, milestones, or other fields using configured provider. Returns confirmation and updated details.
/SKILLUpdates a project state field via TeamMCP with new value and reason, verifies the change, and handles approval flow if not the owner.