| name | removal-path |
| description | Design concrete removal steps for a constraint with timeline and resource needs. |
| execution | subagent |
| prompt | ./prompt.md |
| input | constraint, removability_data |
| dependencies | {"sops":["spawn-agent"]} |
Removal Path
Design a concrete, actionable path to remove or mitigate a constraint. Produces sequenced steps with timeline, resource requirements, and success criteria for each step.
Execution
Spawns a subagent that:
- Receives constraint details and removability assessment
- Selects the best removal approach from those identified
- Decomposes into concrete, sequenced steps
- Estimates timeline and resources for each step
- Defines success criteria and checkpoints
Why Subagent
Removal path design requires creative problem-solving and detailed planning that benefits from focused attention without distraction from other assessment tasks.
HARD-GATE
Output MUST include: at least 3 sequenced steps, timeline estimate, resource requirements, and success criteria for each step. Reject if steps are vague or unactionable.
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
