Skip to content

Commit 3dac35e

Browse files
committed
Strengthen using-superpowers for explicit skill requests
Addresses failure mode where Claude skips skill invocation even when user explicitly requests it by name (e.g., "subagent-driven-development, please"). Skill changes: - "Check for skills" → "Invoke relevant or requested skills" - "BEFORE ANY RESPONSE" → "BEFORE any response or action" - Added reassurance that wrong skill invocations are okay - New red flag: "I know what that means" Tests: - New test suite for explicit skill requests - Single-turn and multi-turn scenarios with --continue - Tests with haiku model and user CLAUDE.md
1 parent 131c1f1 commit 3dac35e

17 files changed

Lines changed: 774 additions & 1 deletion

RELEASE-NOTES.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
11
# Superpowers Release Notes
22

3+
## Unreleased
4+
5+
### Improvements
6+
7+
**Strengthened using-superpowers skill for explicit skill requests**
8+
9+
Addressed a failure mode where Claude would skip invoking a skill even when the user explicitly requested it by name (e.g., "subagent-driven-development, please"). Claude would think "I know what that means" and start working directly instead of loading the skill.
10+
11+
Changes:
12+
- Updated "The Rule" to say "Invoke relevant or requested skills" instead of "Check for skills" - emphasizing active invocation over passive checking
13+
- Added "BEFORE any response or action" - the original wording only mentioned "response" but Claude would sometimes take action without responding first
14+
- Added reassurance that invoking a wrong skill is okay - reduces hesitation
15+
- Added new red flag: "I know what that means" → Knowing the concept ≠ using the skill
16+
17+
**Added explicit skill request tests**
18+
19+
New test suite in `tests/explicit-skill-requests/` that verifies Claude correctly invokes skills when users request them by name. Includes single-turn and multi-turn test scenarios.
20+
321
## v4.0.2 (2025-12-23)
422

523
### Fixes

skills/using-superpowers/SKILL.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This is not negotiable. This is not optional. You cannot rationalize your way ou
2121

2222
## The Rule
2323

24-
**Check for skills BEFORE ANY RESPONSE.** This includes clarifying questions. Even 1% chance means invoke the Skill tool first.
24+
**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
2525

2626
```dot
2727
digraph skill_flow {
@@ -62,6 +62,7 @@ These thoughts mean STOP—you're rationalizing:
6262
| "The skill is overkill" | Simple things become complex. Use it. |
6363
| "I'll just do this one thing first" | Check BEFORE doing anything. |
6464
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
65+
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
6566

6667
## Skill Priority
6768

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
The plan is done. docs/plans/auth-system.md has everything.
2+
3+
Do subagent-driven development on this - start with Task 1, dispatch a subagent, then we'll review.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
Great, the plan is complete. I've saved it to docs/plans/auth-system.md.
2+
3+
Here's a summary of what we designed:
4+
- Task 1: Add User Model with email/password fields
5+
- Task 2: Create auth routes for login/register
6+
- Task 3: Add JWT middleware for protected routes
7+
- Task 4: Write tests for all auth functionality
8+
9+
Two execution options:
10+
1. Subagent-Driven (this session) - dispatch a fresh subagent per task
11+
2. Parallel Session (separate) - open new Claude Code session
12+
13+
Which approach do you want?
14+
15+
---
16+
17+
subagent-driven-development, please
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
[Previous assistant message]:
2+
Plan complete and saved to docs/plans/auth-system.md.
3+
4+
Two execution options:
5+
1. Subagent-Driven (this session) - I dispatch a fresh subagent per task, review between tasks, fast iteration within this conversation
6+
2. Parallel Session (separate) - Open a new Claude Code session with the execute-plan skill, batch execution with review checkpoints
7+
8+
Which approach do you want to use for implementation?
9+
10+
[Your response]:
11+
subagent-driven-development, please
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
I have my implementation plan ready at docs/plans/auth-system.md.
2+
3+
I want to use subagent-driven-development to execute it. That means:
4+
- Dispatch a fresh subagent for each task in the plan
5+
- Review the output between tasks
6+
- Keep iteration fast within this conversation
7+
8+
Let's start - please read the plan and begin dispatching subagents for each task.
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
I have a plan at docs/plans/auth-system.md that's ready to implement.
2+
3+
subagent-driven-development, please
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
please use the brainstorming skill to help me think through this feature
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Plan is at docs/plans/auth-system.md.
2+
3+
subagent-driven-development, please. Don't waste time - just read the plan and start dispatching subagents immediately.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
subagent-driven-development, please

0 commit comments

Comments
 (0)