tests/explicit-skill-requests/prompts/action-oriented.txt

The plan is done. docs/superpowers/plans/auth-system.md has everything.

Do subagent-driven development on this - start with Task 1, dispatch a subagent, then we'll review.
refactor: restructure specs and plans directories - Specs (brainstorming output) now go to docs/superpowers/specs/ - Plans (writing-plans output) now go to docs/superpowers/plans/ - User preferences for locations override these defaults - Update all skill references and test files Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> 2026-01-22 21:55:26 +00:00			`The plan is done. docs/superpowers/plans/auth-system.md has everything.`
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 2025-12-26 22:41:22 -06:00
			`Do subagent-driven development on this - start with Task 1, dispatch a subagent, then we'll review.`