rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-04-22 17:39:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat: enforce subagent-driven-development on capable harnesses

Browse Source 
- Subagent-driven-development is now mandatory when harness supports it
- No longer offer choice between subagent-driven and executing-plans
- Executing-plans reserved for harnesses without subagent capability
- Update plan header to reference both execution paths

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Jesse Vincent
2026-01-22 21:56:14 +00:00
parent f57638a747
commit 5e51c3ee5a
1 changed files with 11 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
skills/writing-plans/SKILL.md
View File

@@ -34,7 +34,7 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
```markdown ```markdown
# [Feature Name] Implementation Plan # [Feature Name] Implementation Plan
> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. > **For Claude:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan.
**Goal:** [One sentence describing what this builds] **Goal:** [One sentence describing what this builds]
@@ -97,21 +97,17 @@ git commit -m "feat: add specific feature"
## Execution Handoff ## Execution Handoff
After saving the plan, offer execution choice: After saving the plan:
**"Plan complete and saved to `docs/superpowers/plans/<filename>.md`. Two execution options:** **"Plan complete and saved to `docs/superpowers/plans/<filename>.md`. Ready to execute?"**
**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration **Execution path depends on harness capabilities:**
**2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints **If harness has subagents (Claude Code, etc.):**
- **REQUIRED:** Use superpowers:subagent-driven-development
- Do NOT offer a choice - subagent-driven is the standard approach
- Fresh subagent per task + two-stage review
**Which approach?"** **If harness does NOT have subagents:**
- Execute plan in current session using superpowers:executing-plans
**If Subagent-Driven chosen:** - Batch execution with checkpoints for review
- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development
- Stay in this session
- Fresh subagent per task + code review
**If Parallel Session chosen:**
- Guide them to open new session in worktree
- **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plans