using-superpowers
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.
Instruction Priority
Superpowers skills override default system prompt behavior, but user instructions always take precedence:
- User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
- Superpowers skills — override default system behavior where they conflict
- Default system prompt — lowest priority
More from pcvelz/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
40writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
37requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
37executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
36subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
35writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
34