An agentic skills framework & software development methodology that works.
Standardize skill frontmatter names to lowercase and kebab-case
Jesse Vincent48410c7f1973
diff --git a/commands/execute-plan.md b/commands/execute-plan.mdindex 0d268a63c..6b24b9835 100644--- a/commands/execute-plan.md+++ b/commands/execute-plan.md@@ -2,4 +2,4 @@description: Execute plan in batches with review checkpoints----Read and follow: ${SUPERPOWERS_SKILLS_ROOT}/skills/collaboration/executing-plans/SKILL.md+Use the executing-plans skill exactly as writtendiff --git a/skills/brainstorming/SKILL.md b/skills/brainstorming/SKILL.mdindex 47e92c6a6..5c3ed7be7 100644--- a/skills/brainstorming/SKILL.md+++ b/skills/brainstorming/SKILL.md@@ -1,5 +1,5 @@----name: Brainstorming+name: brainstormingdescription: IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation---@@ -11,7 +11,7 @@ Transform rough ideas into fully-formed designs through structured questioning a**Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation.-**Announce at start:** "I'm using the Brainstorming skill to refine your idea into a design."+**Announce at start:** "I'm using the brainstorming skill to refine your idea into a design."## The Process@@ -33,7 +33,7 @@ Transform rough ideas into fully-formed designs through structured questioning a### Phase 4: 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."+- Announce: "I'm using the using-git-worktrees skill to set up an isolated workspace."- Switch to skills/collaboration/using-git-worktrees- Follow that skill's process for directory selection, safety verification, and setup- Return here when worktree ready@@ -42,7 +42,7 @@ When design is approved and implementation will follow: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."+- Announce: "I'm using the writing-plans skill to create the implementation plan."- Switch to skills/collaboration/writing-plans skill- Create detailed plan in the worktreediff --git a/skills/commands/brainstorm.md b/skills/commands/brainstorm.mdindex 8800bfc42..e03692bb5 100644--- a/skills/commands/brainstorm.md+++ b/skills/commands/brainstorm.md@@ -1 +1 @@-Use your Brainstorming-Ideas-Into-Designs skill.+Use your brainstorming skill.diff --git a/skills/condition-based-waiting/SKILL.md b/skills/condition-based-waiting/SKILL.mdindex ef6e051f4..1684a5741 100644--- a/skills/condition-based-waiting/SKILL.md+++ b/skills/condition-based-waiting/SKILL.md@@ -1,5 +1,5 @@----name: Condition-Based-Waiting+name: condition-based-waitingdescription: Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses---diff --git a/skills/defense-in-depth/SKILL.md b/skills/defense-in-depth/SKILL.mdindex 0ec613c18..08d69930b 100644--- a/skills/defense-in-depth/SKILL.md+++ b/skills/defense-in-depth/SKILL.md@@ -1,5 +1,5 @@----name: Defense-in-Depth-Validation+name: defense-in-depthdescription: Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible---diff --git a/skills/dispatching-parallel-agents/SKILL.md b/skills/dispatching-parallel-agents/SKILL.mdindex 0f662dbb8..493dea2db 100644--- a/skills/dispatching-parallel-agents/SKILL.md+++ b/skills/dispatching-parallel-agents/SKILL.md@@ -1,5 +1,5 @@----name: Dispatching-Parallel-Agents+name: dispatching-parallel-agentsdescription: Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently---diff --git a/skills/executing-plans/SKILL.md b/skills/executing-plans/SKILL.mdindex 72b8add63..f1fc54513 100644--- a/skills/executing-plans/SKILL.md+++ b/skills/executing-plans/SKILL.md@@ -1,5 +1,5 @@----name: Executing-Plans+name: executing-plansdescription: Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches---@@ -11,7 +11,7 @@ Load plan, review critically, execute tasks in batches, report for review betwee**Core principle:** Batch execution with checkpoints for architect review.-**Announce at start:** "I'm using the Executing Plans skill to implement this plan."+**Announce at start:** "I'm using the executing-plans skill to implement this plan."## The Process@@ -45,7 +45,7 @@ Based on feedback:### Step 5: Complete DevelopmentAfter all tasks complete and verified:-- Announce: "I'm using the Finishing a Development Branch skill to complete this work."+- Announce: "I'm using the finishing-a-development-branch skill to complete this work."- Switch to skills/collaboration/finishing-a-development-branch- Follow that skill to verify tests, present options, execute choicediff --git a/skills/finishing-a-development-branch/SKILL.md b/skills/finishing-a-development-branch/SKILL.mdindex 43925ee7b..9b2f948d7 100644--- a/skills/finishing-a-development-branch/SKILL.md+++ b/skills/finishing-a-development-branch/SKILL.md@@ -1,5 +1,5 @@----name: Finishing-a-Development-Branch+name: finishing-a-development-branchdescription: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup---@@ -11,7 +11,7 @@ Guide completion of development work by presenting clear options and handling ch**Core principle:** Verify tests → Present options → Execute choice → Clean up.-**Announce at start:** "I'm using the Finishing a Development Branch skill to complete this work."+**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."## The Processdiff --git a/skills/receiving-code-review/SKILL.md b/skills/receiving-code-review/SKILL.mdindex 175ebe5e0..85d8b0362 100644--- a/skills/receiving-code-review/SKILL.md+++ b/skills/receiving-code-review/SKILL.md@@ -1,5 +1,5 @@----name: Code-Review-Reception+name: receiving-code-reviewdescription: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation---diff --git a/skills/requesting-code-review/SKILL.md b/skills/requesting-code-review/SKILL.mdindex e6d8b6029..345e44aeb 100644--- a/skills/requesting-code-review/SKILL.md+++ b/skills/requesting-code-review/SKILL.md@@ -1,5 +1,5 @@----name: Requesting-Code-Review+name: requesting-code-reviewdescription: Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent to review implementation against plan or requirements before proceeding---diff --git a/skills/root-cause-tracing/SKILL.md b/skills/root-cause-tracing/SKILL.mdindex 838c6d09e..823ed1eee 100644--- a/skills/root-cause-tracing/SKILL.md+++ b/skills/root-cause-tracing/SKILL.md@@ -1,5 +1,5 @@----name: Root-Cause-Tracing+name: root-cause-tracingdescription: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior---diff --git a/skills/sharing-skills/SKILL.md b/skills/sharing-skills/SKILL.mdindex a2e8963d9..874ce0b16 100644--- a/skills/sharing-skills/SKILL.md+++ b/skills/sharing-skills/SKILL.md@@ -1,5 +1,5 @@----name: Sharing-Skills+name: sharing-skillsdescription: Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository---diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.mdindex 6dcc07908..23529d295 100644--- a/skills/subagent-driven-development/SKILL.md+++ b/skills/subagent-driven-development/SKILL.md@@ -1,5 +1,5 @@----name: Subagent-Driven-Development+name: subagent-driven-developmentdescription: Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates---@@ -102,7 +102,7 @@ After all tasks complete, dispatch final code-reviewer:### 7. Complete DevelopmentAfter final review passes:-- Announce: "I'm using the Finishing a Development Branch skill to complete this work."+- Announce: "I'm using the finishing-a-development-branch skill to complete this work."- Switch to skills/collaboration/finishing-a-development-branch- Follow that skill to verify tests, present options, execute choicediff --git a/skills/systematic-debugging/SKILL.md b/skills/systematic-debugging/SKILL.mdindex b4b34416d..3fe8f30f0 100644--- a/skills/systematic-debugging/SKILL.md+++ b/skills/systematic-debugging/SKILL.md@@ -1,5 +1,5 @@----name: Systematic-Debugging+name: systematic-debuggingdescription: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions---diff --git a/skills/test-driven-development/SKILL.md b/skills/test-driven-development/SKILL.mdindex 6f796a57a..fa8004b16 100644--- a/skills/test-driven-development/SKILL.md+++ b/skills/test-driven-development/SKILL.md@@ -1,5 +1,5 @@----name: Test-Driven-Development+name: test-driven-developmentdescription: Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first---diff --git a/skills/testing-anti-patterns/SKILL.md b/skills/testing-anti-patterns/SKILL.mdindex 90958f799..acf3a98b4 100644--- a/skills/testing-anti-patterns/SKILL.md+++ b/skills/testing-anti-patterns/SKILL.md@@ -1,5 +1,5 @@----name: Testing-Anti-Patterns+name: testing-anti-patternsdescription: Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies---diff --git a/skills/testing-skills-with-subagents/SKILL.md b/skills/testing-skills-with-subagents/SKILL.mdindex 15e0d7ae6..851a30947 100644--- a/skills/testing-skills-with-subagents/SKILL.md+++ b/skills/testing-skills-with-subagents/SKILL.md@@ -1,5 +1,5 @@----name: Testing-Skills-With-Subagents+name: testing-skills-with-subagentsdescription: Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes---diff --git a/skills/using-git-worktrees/SKILL.md b/skills/using-git-worktrees/SKILL.mdindex a9d7da708..cc4d88417 100644--- a/skills/using-git-worktrees/SKILL.md+++ b/skills/using-git-worktrees/SKILL.md@@ -1,5 +1,5 @@----name: Using-Git-Worktrees+name: using-git-worktreesdescription: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification---@@ -11,7 +11,7 @@ Git worktrees create isolated workspaces sharing the same repository, allowing w**Core principle:** Systematic directory selection + safety verification = reliable isolation.-**Announce at start:** "I'm using the Using Git Worktrees skill to set up an isolated workspace."+**Announce at start:** "I'm using the using-git-worktrees skill to set up an isolated workspace."## Directory Selection Process@@ -174,7 +174,7 @@ Ready to implement <feature-name>## Example Workflow```-You: I'm using the Using Git Worktrees skill to set up an isolated workspace.+You: I'm using the using-git-worktrees skill to set up an isolated workspace.[Check .worktrees/ - exists][Verify .gitignore - contains .worktrees/]diff --git a/skills/using-superpowers/SKILL.md b/skills/using-superpowers/SKILL.mdindex ab658d923..54c050168 100644--- a/skills/using-superpowers/SKILL.md+++ b/skills/using-superpowers/SKILL.md@@ -44,8 +44,8 @@ Before using a skill, announce that you are using it."I'm using [Skill Name] to [what you're doing]."**Examples:**-- "I'm using the Brainstorming skill to refine your idea into a design."-- "I'm using the Test-Driven Development skill to implement this feature."+- "I'm using the brainstorming skill to refine your idea into a design."+- "I'm using the test-driven-development skill to implement this feature."**Why:** Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the skill.diff --git a/skills/verification-before-completion/SKILL.md b/skills/verification-before-completion/SKILL.mdindex a1e44c540..2f14076e5 100644--- a/skills/verification-before-completion/SKILL.md+++ b/skills/verification-before-completion/SKILL.md@@ -1,5 +1,5 @@----name: Verification-Before-Completion+name: verification-before-completiondescription: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always---diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.mdindex 811dca8e7..238994ba6 100644--- a/skills/writing-plans/SKILL.md+++ b/skills/writing-plans/SKILL.md@@ -1,5 +1,5 @@----name: Writing-Plans+name: writing-plansdescription: Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge---@@ -11,7 +11,7 @@ Write comprehensive implementation plans assuming the engineer has zero contextAssume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.-**Announce at start:** "I'm using the Writing Plans skill to create the implementation plan."+**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."**Context:** This should be run in a dedicated worktree (created by brainstorming skill).diff --git a/skills/writing-skills/SKILL.md b/skills/writing-skills/SKILL.mdindex 22675d731..01b1d6037 100644--- a/skills/writing-skills/SKILL.md+++ b/skills/writing-skills/SKILL.md@@ -1,5 +1,5 @@----name: Writing-Skills+name: writing-skillsdescription: Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization---