An agentic skills framework & software development methodology that works.
Update all superpowers skill references to use namespace prefix
Jesse Vincent79436abffa0f
diff --git a/skills/brainstorming/SKILL.md b/skills/brainstorming/SKILL.mdindex 2c674ceec..7a05a6710 100644--- a/skills/brainstorming/SKILL.md+++ b/skills/brainstorming/SKILL.md@@ -76,7 +76,7 @@ Options:### Phase 4: Design DocumentationAfter design is validated, write it to a permanent document:-- **File location:** `docs/plans/YYYY-MM-DD-<topic>.md` (use actual date and descriptive topic)+- **File location:** `docs/plans/YYYY-MM-DD-<topic>-design.md` (use actual date and descriptive topic)- **RECOMMENDED SUB-SKILL:** Use elements-of-style:writing-clearly-and-concisely (if available) for documentation quality- **Content:** Capture the design as discussed and validated in Phase 3, organized into the sections that emerged from the conversation- Commit the design document to git before proceeding@@ -84,7 +84,7 @@ After design is validated, write it to a permanent document:### Phase 5: Worktree Setup (for implementation)When design is approved and implementation will follow:- Announce: "I'm using the using-git-worktrees skill to set up an isolated workspace."-- **REQUIRED SUB-SKILL:** Use using-git-worktrees+- **REQUIRED SUB-SKILL:** Use superpowers:using-git-worktrees- Follow that skill's process for directory selection, safety verification, and setup- Return here when worktree ready@@ -93,7 +93,7 @@ Ask: "Ready to create the implementation plan?"When your human partner confirms (any affirmative response):- Announce: "I'm using the writing-plans skill to create the implementation plan."-- **REQUIRED SUB-SKILL:** Use writing-plans+- **REQUIRED SUB-SKILL:** Use superpowers:writing-plans- Create detailed plan in the worktree## Question Patternsdiff --git a/skills/executing-plans/SKILL.md b/skills/executing-plans/SKILL.mdindex b8dd374a8..47e545a67 100644--- a/skills/executing-plans/SKILL.md+++ b/skills/executing-plans/SKILL.md@@ -46,7 +46,7 @@ Based on feedback:After all tasks complete and verified:- Announce: "I'm using the finishing-a-development-branch skill to complete this work."-- **REQUIRED SUB-SKILL:** Use finishing-a-development-branch+- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch- Follow that skill to verify tests, present options, execute choice## When to Stop and Ask for Helpdiff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.mdindex ee5e8d960..1340ada9a 100644--- a/skills/subagent-driven-development/SKILL.md+++ b/skills/subagent-driven-development/SKILL.md@@ -103,7 +103,7 @@ After all tasks complete, dispatch final code-reviewer:After final review passes:- Announce: "I'm using the finishing-a-development-branch skill to complete this work."-- **REQUIRED SUB-SKILL:** Use finishing-a-development-branch+- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch- Follow that skill to verify tests, present options, execute choice## Example Workflowdiff --git a/skills/systematic-debugging/SKILL.md b/skills/systematic-debugging/SKILL.mdindex 636b753cb..15050052c 100644--- a/skills/systematic-debugging/SKILL.md+++ b/skills/systematic-debugging/SKILL.md@@ -111,7 +111,7 @@ You MUST complete each phase before proceeding to the next.**WHEN error is deep in call stack:**- **REQUIRED SUB-SKILL:** Use root-cause-tracing for backward tracing technique+ **REQUIRED SUB-SKILL:** Use superpowers:root-cause-tracing for backward tracing technique**Quick version:**- Where does bad value originate?@@ -176,7 +176,7 @@ You MUST complete each phase before proceeding to the next.- Automated test if possible- One-off test script if no framework- MUST have before fixing- - **REQUIRED SUB-SKILL:** Use test-driven-development for writing proper failing tests+ - **REQUIRED SUB-SKILL:** Use superpowers:test-driven-development for writing proper failing tests2. **Implement Single Fix**- Address the root cause identifieddiff --git a/skills/testing-skills-with-subagents/SKILL.md b/skills/testing-skills-with-subagents/SKILL.mdindex f430ae995..a623adef4 100644--- a/skills/testing-skills-with-subagents/SKILL.md+++ b/skills/testing-skills-with-subagents/SKILL.md@@ -13,7 +13,7 @@ You run scenarios without the skill (RED - watch agent fail), write skill addres**Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill prevents the right failures.-**REQUIRED BACKGROUND:** You MUST understand test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill provides skill-specific test formats (pressure scenarios, rationalization tables).+**REQUIRED BACKGROUND:** You MUST understand superpowers:test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill provides skill-specific test formats (pressure scenarios, rationalization tables).**Complete worked example:** See examples/CLAUDE_MD_TESTING.md for a full test campaign testing CLAUDE.md documentation variants.diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.mdindex 9a8d23193..b26b9d15e 100644--- a/skills/writing-plans/SKILL.md+++ b/skills/writing-plans/SKILL.md@@ -33,7 +33,7 @@ Assume they are a skilled developer, but know almost nothing about our toolset o```markdown# [Feature Name] Implementation Plan-> **For Claude:** REQUIRED SUB-SKILL: Use executing-plans to implement this plan task-by-task.+> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.**Goal:** [One sentence describing what this builds]@@ -107,10 +107,10 @@ After saving the plan, offer execution choice:**Which approach?"****If Subagent-Driven chosen:**-- **REQUIRED SUB-SKILL:** Use subagent-driven-development+- **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 executing-plans+- **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plansdiff --git a/skills/writing-skills/SKILL.md b/skills/writing-skills/SKILL.mdindex 8531eeb86..bb9129c30 100644--- a/skills/writing-skills/SKILL.md+++ b/skills/writing-skills/SKILL.md@@ -15,7 +15,7 @@ You write test cases (pressure scenarios with subagents), watch them fail (basel**Core principle:** If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.-**REQUIRED BACKGROUND:** You MUST understand test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.+**REQUIRED BACKGROUND:** You MUST understand superpowers:test-driven-development before using this skill. That skill defines the fundamental RED-GREEN-REFACTOR cycle. This skill adapts TDD to documentation.**Official guidance:** For Anthropic's official skill authoring best practices, see anthropic-best-practices.md. This document provides additional patterns and guidelines that complement the TDD-focused approach in this skill.@@ -253,8 +253,8 @@ wc -w skills/path/SKILL.md**When writing documentation that references other skills:**Use skill name only, with explicit requirement markers:-- ✅ Good: `**REQUIRED SUB-SKILL:** Use test-driven-development`-- ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand systematic-debugging`+- ✅ Good: `**REQUIRED SUB-SKILL:** Use superpowers:test-driven-development`+- ✅ Good: `**REQUIRED BACKGROUND:** You MUST understand superpowers:systematic-debugging`- ❌ Bad: `See skills/testing/test-driven-development` (unclear if required)- ❌ Bad: `@skills/testing/test-driven-development/SKILL.md` (force-loads, burns context)@@ -357,7 +357,7 @@ Edit skill without testing? Same violation.- Don't "adapt" while running tests- Delete means delete-**REQUIRED BACKGROUND:** The test-driven-development skill explains why this matters. Same principles apply to documentation.+**REQUIRED BACKGROUND:** The superpowers:test-driven-development skill explains why this matters. Same principles apply to documentation.## Testing All Skill Types@@ -520,7 +520,7 @@ Run same scenarios WITH skill. Agent should now comply.Agent found new rationalization? Add explicit counter. Re-test until bulletproof.-**REQUIRED SUB-SKILL:** Use testing-skills-with-subagents for the complete testing methodology:+**REQUIRED SUB-SKILL:** Use superpowers:testing-skills-with-subagents for the complete testing methodology:- How to write pressure scenarios- Pressure types (time, sunk cost, authority, exhaustion)- Plugging holes systematically