Can I ask clarifying questions before invoking a skill?

No, the Skill Orchestrator protocol requires checking for and invoking relevant skills before any response, including clarifying questions, to ensure the skill guides the clarification process.

What is the '1% rule' in this skill?

The rule mandates that if there is even a 1% chance a skill applies to a task, the AI must invoke it immediately before proceeding with any action or response.

Why is this skill necessary for developers?

It prevents 'rationalization'—the tendency to skip complex workflows for 'simple' tasks—ensuring that discipline and domain-specific best practices are never compromised.

How does it handle multiple applicable skills?

It uses a priority system: process skills (like brainstorming or debugging) are invoked first to determine the approach, followed by implementation skills (like frontend design) to guide execution.

Superpowers: Skill Orchestrator

Name: Superpowers: Skill Orchestrator
Author: mance-cyber

bymance-cyber

Productivity & Workflow

Enforces a disciplined workflow by requiring the invocation of relevant skills before any task execution or response.

About

The Skill Orchestrator (Superpowers) is a meta-skill designed to ensure Claude Code consistently utilizes specialized domain knowledge and patterns. It establishes a rigorous 'skill-first' protocol where the AI must check for and invoke relevant skills even if there is only a 1% chance of applicability. By preventing the AI from skipping workflows or 'rationalizing' its way out of standard procedures, this skill ensures that best practices, checklists, and specialized tools are applied to every interaction before any code is written or questions are asked.

Key Features

Pre-response check for a '1% chance' of skill applicability
Standardized prioritization logic for multiple applicable skills
Mandatory skill discovery and invocation protocols
0 GitHub stars
Rationalization detection to prevent skipping workflows
Automatic todo-list generation from skill checklists

Use Cases

Preventing technical debt by forcing adherence to defined development workflows
Ensuring complex coding tasks always follow architectural patterns or TDD
Standardizing team interactions with shared project-specific skills

About

Key Features

Pre-response check for a '1% chance' of skill applicability
Standardized prioritization logic for multiple applicable skills
Mandatory skill discovery and invocation protocols
0 GitHub stars
Rationalization detection to prevent skipping workflows
Automatic todo-list generation from skill checklists

Use Cases

Preventing technical debt by forcing adherence to defined development workflows
Ensuring complex coding tasks always follow architectural patterns or TDD
Standardizing team interactions with shared project-specific skills