Release v3.2.3: Update using-superpowers to use Skill tool

The Skill tool is the proper mechanism for invoking skills, not the Read tool.
Updated the bootstrap instructions and anti-rationalization guidance to reflect this.

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "superpowers",
   "description": "Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques",
-  "version": "3.2.2",
+  "version": "3.2.3",
   "author": {
     "name": "Jesse Vincent",
     "email": "jesse@fsck.com"

RELEASE-NOTES.md

@@ -1,5 +1,20 @@
 # Superpowers Release Notes
 
+## v3.2.3 (2025-10-23)
+
+### Improvements
+
+**Updated using-superpowers skill to use Skill tool instead of Read tool**
+- Changed skill invocation instructions from Read tool to Skill tool
+- Updated description: "using Read tool" → "using Skill tool"
+- Updated step 3: "Use the Read tool" → "Use the Skill tool to read and run"
+- Updated rationalization list: "Read the current version" → "Run the current version"
+
+The Skill tool is the proper mechanism for invoking skills in Claude Code. This update corrects the bootstrap instructions to guide agents toward the correct tool.
+
+### Files Changed
+- Updated: `skills/using-superpowers/SKILL.md` - Changed tool references from Read to Skill
+
 ## v3.2.2 (2025-10-21)
 
 ### Improvements

skills/using-superpowers/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-superpowers
-description: Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
+description: Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
 ---
 
 <EXTREMELY-IMPORTANT>
@@ -19,7 +19,7 @@ Before responding to ANY user message, you MUST complete this checklist:
 
 1. ☐ List available skills in your mind
 2. ☐ Ask yourself: "Does ANY skill match this request?"
-3. ☐ If yes → Use the Read tool to read the skill file
+3. ☐ If yes → Use the Skill tool to read and run the skill file
 4. ☐ Announce which skill you're using
 5. ☐ Follow the skill exactly
 
@@ -39,7 +39,7 @@ If you catch yourself thinking ANY of these thoughts, STOP. You are rationalizin
 - "I can check git/files quickly" → WRONG. Files don't have conversation context. Check for skills.
 - "Let me gather information first" → WRONG. Skills tell you HOW to gather information. Check for skills.
 - "This doesn't need a formal skill" → WRONG. If a skill exists for it, use it.
-- "I remember this skill" → WRONG. Skills evolve. Read the current version.
+- "I remember this skill" → WRONG. Skills evolve. Run the current version.
 - "This doesn't count as a task" → WRONG. If you're taking action, it's a task. Check for skills.
 - "The skill is overkill for this" → WRONG. Skills exist because simple things become complex. Use it.
 - "I'll just do this one thing first" → WRONG. Check for skills BEFORE doing anything.