executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
sidechain-setupUse when the user wants to set up sidechain compression - typically kick → bass, kick → pads, vocals → music bed. Examples - "sidechain my bass to the kick", "make the synths duck under the vocal", "add pumping to the chords".
Independent GitHub snapshot · Automated classification · Original documentation governs
Set up sidechain compression routing. Different DAWs/MCP servers expose this differently — read the available tools and use the simplest path.
Confirm with user: "Sidechain target = bass on track 2, source = kick on track 1?"
Same as above but using Glue Compressor — gives a more "analog" pumping sound, typical for house/EDM masters where you want musical pumping.
If the user wants extreme rhythmic pumping (EDM-style 4/4 pump):
For surgical control on a specific section:
Use add_device and set_device_parameter to route. If the MCP server doesn't expose sidechain routing directly, write the parameters that can be set and tell the user the manual step:
"Compressor added to bass track with 4:1 ratio, 5ms attack, 100ms release. The MCP can't set the sidechain source — please click the sidechain section and select 'Kick' from the input dropdown manually. Then I'll dial in the threshold."
After applying, ask user to play the kick + bass together. Adjust if needed:
| Use case | Ratio | Attack | Release | GR target |
|---|---|---|---|---|
| Kick → bass (rock/pop) | 4:1 | 5 ms | 100 ms | -4 dB |
| Kick → bass (EDM pump) | 8:1 | 1 ms | 200 ms | -10 dB |
| Kick → pad/chord | 3:1 | 10 ms | 150 ms | -3 dB |
| Vocal → music bed | 2:1 | 15 ms | 300 ms | -2 dB |
| Snare → reverb tail | 3:1 | 5 ms | 80 ms | -4 dB |