subagent-driven-development
Subagent-Driven Development
When to Use
- Task has 2+ independent workstreams
- Each workstream takes >10 minutes
- Workstreams do not share mutable state
The Pattern
- Decompose - break into independent subtasks
- Spec each subagent - clear, self-contained instructions
- Launch in parallel - use exec with background:true
- Monitor - check progress, do not micromanage
- Integrate - run full test suite after all complete
Launch Pattern
exec command:"claude --permission-mode bypassPermissions --print '[spec A]'" background:true
exec command:"claude --permission-mode bypassPermissions --print '[spec B]'" background:true
More from archieindian/openclaw-superpowers
heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
25context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
25fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
19long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
19agent-self-recovery
Detects when the agent is stuck in a loop and escapes systematically. Use when you notice repeated failures or loss of direction.
18skill-vetting
Reviews a ClawHub skill's source code for security risks before installation. Use before installing any new skill.
18