Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From majestic-engineer
Executes epic tasks from blueprint using fresh Claude instances via relay script, with quality gate verification and configurable retries.
How this command is triggered — by the user, by Claude, or both
Slash command
/majestic-engineer:work [task_id] [--max-attempts N]relay/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
# Execute Epic Tasks ## Input ## Workflow ## Task Coordination Workers share a TaskList via environment variable: Workers can discover and log additional work: - Use `TaskCreate` for discovered work outside current task scope - Continue with current task - do NOT block on discoveries - Orchestrator sees discovered tasks after worker completes **Note:** Ledger tracks detailed attempt receipts. Tasks enable worker-to-orchestrator communication. ## Error Handling | Scenario | Action | |----------|--------| | No pending tasks | Report status, check for gated tasks | | All tasks bl...
task_id: string # Optional: T1, T2 (run specific task)
max_attempts: int # Optional: Override default (3)
If not exists(".agents/relay/epic.yml"):
Error: "No epic found. Run `/majestic-relay:init <blueprint.md>` first."
If not exists(".agents/relay/attempt-ledger.yml"):
Error: "Ledger missing. Run `/majestic-relay:init <blueprint.md>` to reinitialize."
Execute: "${CLAUDE_PLUGIN_ROOT}/scripts/relay/relay-work.sh" $ARGUMENTS
Workers share a TaskList via environment variable:
export CLAUDE_CODE_TASK_LIST_ID="relay-${EPIC_ID}"
Workers can discover and log additional work:
TaskCreate for discovered work outside current task scopeNote: Ledger tracks detailed attempt receipts. Tasks enable worker-to-orchestrator communication.
| Scenario | Action |
|---|---|
| No pending tasks | Report status, check for gated tasks |
| All tasks blocked | Report dependency chain |
| Quality gate: NEEDS CHANGES | Retry with findings |
| Quality gate: BLOCKED | Gate task immediately |
| Ctrl+C | Save state, exit cleanly |
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineer/amoa-orchestrator-loopStarts a persistent orchestrator loop that monitors tasks across Claude Tasks, GitHub issues, and markdown checklist files, preventing exit until all sources are complete.
/continueAutonomously executes pending tasks from orchestrator queue, delegating to agents like frontend-dev or backend-dev, with git checks, retries, and quality gates until completion or pause.
/workExecutes a development plan end-to-end with checks for <fn-N or idea>. Supports --branch (current|new|worktree) and --review (rp|export|none) options.
/workAuto-classifies tasks from descriptions, folder paths, or issue IDs and routes to workflow orchestrators; resumes existing tasks from .maister folders.
/workAuto-classifies tasks from descriptions, folder paths, or issue identifiers (GitHub/Jira/Azure DevOps) and routes to workflow orchestrators. Resumes existing tasks.
/workExecutes a work plan from a plan/spec/todo file path: clarifies requirements, sets up git branch or worktree, generates prioritized todos, and completes tasks maintaining quality.