using-superpowers

Enforces skill discovery and invocation before any agent response or action.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill using-superpowers-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/superpowers/skills/using-superpowers
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill using-superpowers-kxnzee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often skip available skills and answer directly, producing inconsistent or undisciplined results. This Skill establishes a mandatory workflow that forces the agent to check for and invoke relevant skills before any response, including clarifying questions or codebase exploration. ## Core Features & Use Cases - Mandatory Skill Invocation: Requires checking for applicable skills before any response, with a red-flag table that catches common rationalizations for skipping them. - Skill Priority Rules: Defines ordering where process skills (brainstorming, systematic-debugging) run before implementation skills. - OpenSpec Routing: Resolves the current OpenSpec schema and artifact instructions first, governing skill selection, output paths, and lifecycle. - Use Case: When a user says "fix this bug", the agent invokes systematic-debugging first instead of jumping straight into editing code. ## Quick Start Start a new conversation and let the agent check for applicable skills before responding to your request.

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 agent always check for skills before responding?▼

Install a meta-skill like this one that mandates skill invocation before any response, including clarifying questions. It defines a rule that relevant skills must be invoked first and lists rationalizations to reject.

What is the correct order for invoking process and implementation skills?▼

Process skills come first because they set the approach, then implementation skills carry it out. For example, brainstorming precedes frontend-design, and systematic-debugging precedes domain-specific fix skills.

Does this skill apply to subagents dispatched for specific tasks?▼

No. The skill explicitly instructs subagents dispatched to execute a specific task to ignore it, so delegated execution is not interrupted by the skill-discovery workflow.

How does this skill interact with OpenSpec changes?▼

For an OpenSpec change, the agent resolves the current schema and artifact instructions first, which govern skill selection, output paths, and lifecycle. Accepted intents, requirements, or plans do not retrigger brainstorming.

When can skill workflows be skipped?▼

Only when the user explicitly instructs it. User instructions in files like CLAUDE.md or AGENTS.md take precedence over skills, which in turn override default agent behavior.