When should I invoke the Superpowers skill?

It should be invoked at the very beginning of any new conversation or task to establish the correct workflow protocol.

What is the primary purpose of the Superpowers skill?

It is a meta-skill designed to ensure Claude always checks for and uses other relevant specialized skills before taking any action or answering questions.

Why is this skill considered 'mandatory' by its own rules?

To prevent 'rationalization' where the AI might skip a helpful skill because a task seems simple, ensuring consistent quality and discipline.

Does it work with clarifying questions?

Yes, the skill requires checking for relevant domain skills even before asking the user for more context or clarification.

How does this skill handle multiple relevant skills?

It dictates a specific priority: process-oriented skills (like brainstorming or debugging) are invoked first, followed by implementation-specific skills.

Superpowers Skill Orchestrator

Name: Superpowers Skill Orchestrator
Author: zoosewu

byzoosewu

Productivity & Workflow

Enforces a disciplined protocol for discovering and invoking specialized skills before performing any task in Claude Code.

About

The Superpowers skill acts as a foundational meta-layer for Claude Code, ensuring that domain-specific expertise is never overlooked. It establishes a mandatory workflow that requires the AI to check for applicable skills even if there is only a 1% chance of relevance. By identifying common rationalizations for skipping protocols and providing a clear priority for process versus implementation skills, it ensures that every task—from simple questions to complex refactors—benefits from the most relevant best practices and checklists available in the environment.

Key Features

Requires skill checks before providing even clarifying questions
0 GitHub stars
Mandates Skill tool invocation at the start of every conversation
Identifies and neutralizes common rationalizations for skipping workflows
Standardizes the use of checklists through TodoWrite integration
Establishes a clear priority hierarchy for multi-skill scenarios

Use Cases

Enforcing strict adherence to Test-Driven Development or debugging protocols
Maximizing the utility of specialized domain skills during complex project initialization
Standardizing team-wide coding patterns by preventing skipped workflows

About

Key Features

Requires skill checks before providing even clarifying questions
0 GitHub stars
Mandates Skill tool invocation at the start of every conversation
Identifies and neutralizes common rationalizations for skipping workflows
Standardizes the use of checklists through TodoWrite integration
Establishes a clear priority hierarchy for multi-skill scenarios

Use Cases

Enforcing strict adherence to Test-Driven Development or debugging protocols
Maximizing the utility of specialized domain skills during complex project initialization
Standardizing team-wide coding patterns by preventing skipped workflows