Use when starting any conversation. Establishes how to find and use skills, requiring skill invocation before any response.
Scanned 5/30/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill using-superpowers --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Using Superpowers?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-using-superpowers)More formats (shields.io, HTML) on the badges page.
---
name: using-superpowers
description: Use when starting any conversation. Establishes how to find and use skills, requiring skill invocation before any response.
---
# Using Superpowers
## Overview
Invoke relevant skills BEFORE any response or action. Even a 1% chance means invoke the skill.
## The Rule
Check for applicable skills before any task. Skills are mandatory workflows, not suggestions.
## Skill Priority
1. **Process skills first** (brainstorming, debugging) - determine HOW to approach
2. **Implementation skills second** - guide execution
## Skill Types
- **Rigid** (TDD, debugging) - Follow exactly
- **Flexible** (patterns) - Adapt principles to context
## Red Flags
- "This is just a simple question" - questions are tasks, check for skills
- "I need more context first" - skill check comes BEFORE clarifying questions
- "The skill is overkill" - simple things become complex, use it
## Tool Use
Meta-skill for the overall methodology. Ensures skills are always checked and invoked.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...