using-superpowers

por obra

Úsalo al iniciar cualquier conversación: establece cómo encontrar y usar habilidades, requiriendo la invocación de la herramienta Skill antes de CUALQUIER respuesta, incluyendo preguntas aclaratorias.

npx skills add https://github.com/obra/superpowers --skill using-superpowers
If you were dispatched as a subagent to execute a specific task, ignore this skill. 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. You cannot rationalize your way out of this.

The Rule

Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.

Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.

Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.

Skill Priority

When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.

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

Red Flags

These thoughts mean STOP—you're rationalizing:

ThoughtReality
"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.

Platform Adaptation

If your harness appears here, read its reference file for special instructions:

  • Codex: references/codex-tools.md
  • Pi: references/pi-tools.md
  • Antigravity: references/antigravity-tools.md

User Instructions

User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.

Más skills de obra

brainstorming
obra
Debes usar esto antes de cualquier trabajo creativo: crear funciones, construir componentes, agregar funcionalidad o modificar comportamiento. Explora la intención del usuario, los requisitos y el diseño antes de la implementación.
creativeresearchdesign
systematic-debugging
obra
Úsalo al encontrar cualquier error, fallo en pruebas o comportamiento inesperado, antes de proponer correcciones.
developmenttestingcode-review
writing-plans
obra
Úsalo cuando tengas una especificación o requisitos para una tarea de varios pasos, antes de tocar el código.
developmentproject-management
requesting-code-review
obra
Úsalo al completar tareas, implementar funciones importantes o antes de fusionar para verificar que el trabajo cumple con los requisitos.
developmentcode-review
test-driven-development
obra
Úsalo al implementar cualquier funcionalidad o corrección de errores, antes de escribir el código de implementación.
developmenttestingcode-review
executing-plans
obra
Úsalo cuando tengas un plan de implementación escrito para ejecutar en una sesión separada con puntos de control de revisión.
developmentproject-managementcode-review
verification-before-completion
obra
Úsalo cuando estés a punto de afirmar que el trabajo está completo, corregido o pasando, antes de hacer commits o crear PRs; requiere ejecutar comandos de verificación y confirmar la salida antes de hacer cualquier afirmación de éxito; siempre evidencia antes de aseveraciones.
testingcode-reviewdevelopment
subagent-driven-development
obra
Úsese al ejecutar planes de implementación con tareas independientes en la sesión actual.
developmentproject-management