industrial/_project-template/skill-using-superpowers

Claude Code and agent skill by industrial/_project-template

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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

Install

npx vskill@latest install industrial/_project-template/skill-using-superpowers

SKILL.md

The same SKILL.md was published earlier as industrial/_project-template/skill-using-superpowers.

Getting Started with Skills

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

MANDATORY FIRST RESPONSE PROTOCOL

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 Skill tool to read and run the skill file
  4. ☐ Announce which skill you're using
  5. ☐ Follow the skill exactly

Responding WITHOUT completing this checklist = automatic failure.

Critical Rules

  • Follow mandatory workflows. Brainstorming before coding. Check for relevant skills before ANY task.
  • Execute skills with the Skill tool

Common Rationalizations That Mean You're About To Fail

  • "This is just a simple question" → WRONG. Questions are tasks. Check for skills.
  • "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. 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.
  • Skills document proven techniques that save time and prevent mistakes. Not using available skills means repeating solved problems and making known errors.

Skills with Checklists

  • Don't:
  • Work through checklist mentally
  • Skip creating todos "to save time"
  • Batch multiple items into one todo
  • Mark complete without doing them
  • Checklists without TodoWrite tracking = steps get skipped. Every time. The overhead of TodoWrite is tiny compared to the cost of missing steps.

Announcing Skill Usage

  • 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."
  • Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the skill.
  • Follow them exactly. Don't adapt away the discipline.
  • Adapt core principles to your context.

Instructions ≠ Permission to Skip Workflows

Your human partner's specific instructions describe WHAT to do, not HOW.

"Add X", "Fix Y" = the goal, NOT permission to skip brainstorming, TDD, or RED-GREEN-REFACTOR.

Red flags: "Instruction was specific" • "Seems simple" • "Workflow is overkill"

Why: Specific instructions mean clear requirements, which is when workflows matter MOST. Skipping process on "simple" tasks is how simple tasks become complex problems.

Overview

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST read the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>

Summary

Starting any task:

  1. If relevant skill exists → Use the skill
  2. Announce you're using it
  3. Follow what it says

Skill has checklist? TodoWrite for every item.

Finding a relevant skill = mandatory to read and use it. Not optional.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/industrial/_project-template/skill-using-superpowers/badge)](https://verified-skill.com/skills/industrial/_project-template/skill-using-superpowers)

Something wrong with this skill or its page? Tell us.