skills.rest
involvex
involvexCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

using-superpowers

Enforces skill discovery and invocation before any AI response or task execution.

Updated Mar 1, 2026
Search Tags:#AI assistant#workflow enforcement#skill discovery#todowrite#skill invocation#process discipline#conversation protocol
One-click install
npx skills add https://github.com/involvex/dev --skill using-superpowers-involvex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/involvex/dev/tree/main/.claude/skills/using-superpowers
Command: npx skills add https://github.com/involvex/dev --skill using-superpowers-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants often skip available skills and respond directly, missing established workflows and producing inconsistent results. This Skill establishes a mandatory discipline of checking for and invoking relevant skills before any response, including clarifying questions. ## Core Features & Use Cases - Mandatory Skill Check: Requires invoking the Skill tool before any response when there is even a small chance a skill applies. - Decision Flowchart: Provides a visual flow for deciding when to invoke skills, announce usage, and convert checklists into TodoWrite todos. - Rationalization Detection: Lists common red-flag thoughts that signal you are skipping skills, plus a priority order for process skills versus implementation skills. - Use Case: When a user asks to build a feature or fix a bug, the assistant first invokes the brainstorming or debugging skill before writing any code, ensuring the correct workflow is followed. ## Quick Start Before responding to my request, check whether any available skill applies and invoke it first.

Frequently Asked Questions about using-superpowers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI assistant always check for skills before responding?▼

Use a mandatory skill-check rule that requires invoking the Skill tool before any response, including clarifying questions. The rule treats even a small chance of relevance as grounds for invocation and blocks rationalizations like "this is just a simple question."

What is the correct order when multiple skills apply to one task?▼

Process skills such as brainstorming and debugging come first because they determine how to approach the task. Implementation skills like frontend-design or mcp-builder come second to guide execution.

Should I check for skills before asking clarifying questions?▼

Yes, the skill check comes before clarifying questions. Skills often tell you how to gather information and explore a codebase, so skipping the check loses that guidance.

What is the difference between rigid and flexible skills?▼

Rigid skills like TDD and debugging must be followed exactly without adapting away their discipline. Flexible skills describe patterns whose principles can be adapted to the context, and the skill itself indicates which type it is.

When should a skill checklist become TodoWrite todos?▼

When an invoked skill contains a checklist, create one TodoWrite todo per checklist item after announcing skill usage. Then follow the skill exactly before responding to the user.

Related Skills

Explore More Software Engineering Skills→
fyodorivfyodoriv

agentbrew-add-skill

Register GitHub, local folder, and catalog skill sources for agentbrew deployment.

Community
Intermediate
sadie100sadie100

spec-pipeline

Execute a requirement-to-implementation pipeline using sequential subagents for brainstorming, grilling, planning, and execution.

Community
Advanced
xiaoyuge886xiaoyuge886
196

todo-master

Manages task planning, decomposition, and status via TodoWrite.

Community
Intermediate
costrict-plugins-repocostrict-plugins-repo

using-superpowers

Invoke relevant skills before producing user-facing responses across runtimes.

Official
Intermediate