using-superpowers
Scannednpx machina-cli add skill a5c-ai/babysitter/using-superpowers --openclawUsing Superpowers
Overview
Invoke relevant skills BEFORE any response or action. Even a 1% chance means invoke the skill.
The Rule
Check for applicable skills before any task. Skills are mandatory workflows, not suggestions.
Skill Priority
- Process skills first (brainstorming, debugging) - determine HOW to approach
- Implementation skills second - guide execution
Skill Types
- Rigid (TDD, debugging) - Follow exactly
- Flexible (patterns) - Adapt principles to context
Red Flags
- "This is just a simple question" - questions are tasks, check for skills
- "I need more context first" - skill check comes BEFORE clarifying questions
- "The skill is overkill" - simple things become complex, use it
Tool Use
Meta-skill for the overall methodology. Ensures skills are always checked and invoked.
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/superpowers/skills/using-superpowers/SKILL.mdView on GitHub Overview
Using Superpowers ensures you check for applicable skills and invoke them before any response. Skills are mandatory workflows that guide how to approach and execute tasks, not optional hints. Always start by prioritizing Process skills, then move to Implementation skills.
How This Skill Works
Before addressing any task, scan for applicable skills and invoke the most relevant one. Treat skills as mandatory workflows: start with Process skills (brainstorming, debugging) to determine HOW, then use Implementation skills to guide execution. The meta-skill (Tool Use) enforces consistent skill invocation.
When to Use It
- At the start of a new conversation to establish how to find and use skills.
- When a task benefits from brainstorming or debugging to determine the best approach.
- Before execution, use an implementation skill to guide steps and methods.
- Before asking clarifying questions, invoke applicable skills to frame the problem.
- When a request seems simple or context-free, trigger skills to ensure a proper workflow.
Quick Start
- Step 1: Identify applicable skills for the current task and invoke the most relevant.
- Step 2: Apply the chosen Process skill (e.g., brainstorming or debugging) to determine HOW.
- Step 3: Proceed with the Implementation skill to execute and respond.
Best Practices
- Always check for applicable skills before any response.
- Prioritize Process skills first (brainstorming, debugging), then Implementation skills.
- Treat skills as mandatory workflows, not optional hints.
- Differentiate between Rigid and Flexible skills and apply them appropriately.
- Use the meta-skill Tool Use to enforce consistent skill invocation.
Example Use Cases
- Starting a chat about a code issue, invoke a brainstorming or debugging skill to outline steps.
- Entering a new domain: invoke a discovery skill to identify relevant capabilities.
- Debugging a failing feature: call a process skill to brainstorm fixes before coding.
- Facing ambiguous input: invoke a planning skill to structure the response before answering.
- A user claims a request is 'simple'—still trigger skills to ensure a proper workflow.