using-superpowers

Enforce mandatory skill checks before any AI response or action.

Updated May 28, 2026
One-click install
npx skills add https://github.com/kyo0221/claude-config --skill using-superpowers-kyo0221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/kyo0221/claude-config/tree/main/skills/using-superpowers
Command: npx skills add https://github.com/kyo0221/claude-config --skill using-superpowers-kyo0221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents AI from skipping relevant skills during interactions, which causes inefficient workflows, non-compliant task execution, and wasted effort from using incorrect or unapproved approaches.

Core Features & Use Cases

  • Mandatory Pre-Action Skill Check: Requires invoking applicable skills before any response, action, or clarifying question, even for seemingly trivial tasks.
  • Clear Priority Hierarchy: Establishes that user instructions always take precedence over skill rules, and process-focused skills (e.g., debugging, brainstorming) are prioritized over implementation skills when multiple apply.
  • Anti-Rationalization Guardrails: Lists common excuses for skipping skills and their corrections to stop undisciplined, premature action.
  • Use Case: When asked to add a new feature to a codebase, this skill ensures you first invoke the brainstorming skill to plan the implementation, rather than immediately writing code without proper design.

Quick Start

Before responding to any user request or taking any action, first check if any installed skills apply to the task and invoke them using the appropriate Skill tool for your platform.

Frequently Asked Questions about using-superpowers

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

FAQPage Schema
How do I enforce skill invocation before Claude Code or Copilot CLI generates a response?

Mandatory pre-action skill checks enforce skill invocation before any AI response, preventing skipped workflows. This requires checking installed skills before answering or taking action, ensuring consistent process adherence across CLI platforms.

Why does my AI task management workflow skip relevant skills during simple debugging tasks?

AI often skips skills during simple debugging tasks due to rationalization, assuming trivial requests don't need process adherence. Anti-rationalization guardrails counter these common excuses, requiring mandatory skill checks for all task types to prevent non-compliant execution.

What is the priority hierarchy when multiple skills apply to an implementation task in Gemini CLI?

The priority hierarchy establishes that user instructions always take precedence over skill rules. When multiple skills apply, process-focused skills like brainstorming or debugging are prioritized over implementation skills to ensure proper design before coding.

Does mandatory skill checking work across different AI CLI tools like Gemini CLI and Copilot CLI?

Mandatory skill checking applies across multiple platforms including Claude Code, Copilot CLI, and Gemini CLI. It enforces consistent workflow adherence and user instruction priority before any response or action, regardless of the supported CLI environment.

How to stop AI from writing code without first invoking the brainstorming skill for new features?

To stop premature coding, mandatory pre-action checks require invoking applicable process-focused skills like brainstorming before implementation work. This enforces proper planning and design first, eliminating undisciplined action and inefficient workflows.

What are the limitations of using process adherence guardrails for AI task execution?

Process adherence guardrails depend on the AI's willingness to follow mandatory skill checks before acting. While anti-rationalization measures list common excuses and corrections, ultimate enforcement still relies on the platform's ability to strictly execute the pre-action check requirement.