Using Superpowers

---
skill_id: engineering_agentops.using-superpowers
name: using-superpowers
description: "Use — Introdução ao sistema de skills Superpowers: como as skills são ativadas automaticamente,"
  Introdução ao sistema de skills Superpowers: como as skills são ativadas automaticamente,
  o workflow básico (brainstorming → worktrees → writing-plans → SDD → TDD → review →
  finishing), e referências por plataforma (Claude Code, Codex, Gemini, Copilot).
version: v00.36.0
status: ADOPTED
domain_path: engineering_agentops/using-superpowers
source_repo: obra/superpowers
risk: safe
tier: ADAPTED
anchors:
  - superpowers
  - workflow_overview
  - skill_system
  - onboarding
  - meta_skill
  - getting_started
cross_domain_bridges:
  - to: engineering_agentops.brainstorming
    strength: 0.85
    reason: "primeiro skill do workflow principal — using-superpowers apresenta o sistema"
  - to: apex_internals.skill_registry
    strength: 0.80
    reason: "análogo ao skill_registry do APEX — gerencia qual skill usar em cada contexto"
  - to: apex_internals.cognitive_mode_selector
    strength: 0.75
    reason: "seleção automática de skill é similar à seleção de cognitive_mode do APEX"
input_schema:
  - name: platform
    type: string
    description: "Plataforma em uso: CLAUDE_CODE | CODEX | GEMINI | COPILOT | OTHER"
    required: false
  - name: user_intent
    type: string
    description: "O que o usuário quer fazer (para determinar qual skill invocar)"
    required: false
output_schema:
  - name: recommended_skill
    type: string
    description: "Skill recomendada para o contexto atual"
  - name: workflow_overview
    type: string
    description: "Visão geral do workflow completo para o tipo de tarefa"
what_if_fails: >
  Se plataforma não reconhecida: usar CLAUDE_CODE como padrão.
  Se intent não mapeia claramente para uma skill: usar brainstorming como ponto de entrada universal.
synergy_map:
  - type: skill
    ref: engineering_agentops.brainstorming
    benefit: "ponto de entrada principal do workflow"
  - type: skill
    ref: engineering_agentops.writing-skills
    benefit: "criar novas skills quando necessário — meta-skill complementar"
security:
  - risk: "Usuário confundido sobre qual skill usar pode iniciar processo errado"
    mitigation: "brainstorming é o fallback universal seguro para qualquer intent ambíguo"
executor: LLM_BEHAVIOR
---

<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, skip this skill.
</SUBAGENT-STOP>

<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>

## Instruction Priority

Superpowers skills override default system prompt behavior, but **user instructions always take precedence**:

1. **User's explicit instructions** (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
2. **Superpowers skills** — override default system behavior where they conflict
3. **Default system prompt** — lowest priority

If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.

## How to Access Skills

**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.

**In Copilot CLI:** Use the `skill` tool. Skills are auto-discovered from installed plugins. The `skill` tool works the same as Claude Code's `Skill` tool.

**In Gemini CLI:** Skills activate via the `activate_skill` tool. Gemini loads skill metadata at session start and activates the full content on demand.

**In other environments:** Check your platform's documentation for how skills are loaded.

## Platform Adaptation

Skills use Claude Code tool names. Non-CC platforms: see `references/copilot-tools.md` (Copilot CLI), `references/codex-tools.md` (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.

# Using Skills

## The Rule

**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

```dot
digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to EnterPlanMode?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke brainstorming skill" [shape=box];
    "Might any skill apply?" [shape=diamond];
    "Invoke Skill tool" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create TodoWrite todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "About to EnterPlanMode?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
    "Invoke brainstorming skill" -> "Might any skill apply?";

    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create TodoWrite todo per item" -> "Follow skill exactly";
}
```

## Red Flags

These thoughts mean STOP—you're rationalizing:

| Thought | Reality |
|---------|---------|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |

## Skill Priority

When multiple skills could apply, use this order:

1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution

"Let's build X" → brainstorming first, then implementation skills.
"Fix this bug" → debugging first, then domain-specific skills.

## Skill Types

**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.

**Flexible** (patterns): Adapt principles to context.

The skill itself tells you which.

## User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.

---

## Why This Skill Exists

Use — Introdução ao sistema de skills Superpowers: como as skills são ativadas automaticamente,

<!-- SR_40: auto-generated from frontmatter `purpose`/`description` (OPP-Phase3). Expand with domain-specific rationale. -->

## When to Use

Use this skill when the task requires using superpowers capabilities.

<!-- SR_40: auto-generated from frontmatter `when`/`description` (OPP-Phase3). -->

## What If Fails

Se plataforma não reconhecida: usar CLAUDE_CODE como padrão.

<!-- SR_40: auto-generated from frontmatter `what_if_fails` (OPP-Phase3). -->