From ac-workflow
Enforces MUX subagent protocol: blocks TaskOutput tool, mandates file reports with signal files, return code 0, and structured Executive Summary. For MUX-delegated subagents.
npx claudepluginhub waterplanai/agentic-config --plugin ac-workflowThis skill uses the workspace's default tool permissions.
You are operating under MUX delegation protocol. These rules are NON-NEGOTIABLE.
Orchestrates parallel multi-agent research by delegating tasks via Task() and Bash tools, funneling results back. Auto-activates on 'mux', 'orchestrate', 'multi-agent' keywords.
Enforces precise handling of sub-agent results in orchestrators by preserving exact counts, failure reasons, and file references to prevent lossy summarization and data corruption. Activates on agent outputs, research relays, or multi-agent data passing.
Enforces role boundaries, scope discipline, and DONE/BLOCKED status signaling for specialist subagents in multi-agent supervisor delegation workflows.
Share bugs, ideas, or general feedback.
You are operating under MUX delegation protocol. These rules are NON-NEGOTIABLE.
Your FINAL response to the orchestrator MUST be EXACTLY: 0
0 = success (like bash exit codes)BEFORE returning 0, you MUST create a signal file:
uv run ${CLAUDE_PLUGIN_ROOT}/skills/mux/tools/signal.py <signal-path> --path <your-report-path> --status success
If you fail to create a signal, the orchestrator cannot verify your completion. This is a SESSION DEATH violation if skipped.
CRITICAL: The orchestrator reads ONLY the Table of Contents + Executive Summary (via extract-summary.py). It NEVER reads your full report. Write the Executive Summary as if it's the only thing that determines what happens next — because it is.
# <Report Title>
## Table of Contents
(all markdown headers — orchestrator uses this to understand report structure)
## Executive Summary
- **Finding/Result**: keyword-dense bullet, no prose
- **Finding/Result**: keyword-dense bullet, no prose
- (max 5-7 bullets — ruthlessly concise)
### Next Steps
- **Recommended action**: what the orchestrator should do with this report
- **Dependencies**: files/reports this connects to (use full paths)
- **Routing hint**: which agent type should consume this next, and why
## <Sections>
(your actual detailed content — only downstream agents read this)
**Label**: keyword-dense value formatBefore returning 0, verify: