obra/superpowers

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

• SKILL.md.md

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• SKILL.md.md

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• SKILL.md.md

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

• SKILL.md.md

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• SKILL.md.md

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• SKILL.md.md
• code-reviewer.md.md

Use when implementing any feature or bugfix, before writing implementation code

• SKILL.md.md
• testing-anti-patterns.md.md

Use when you have a spec or requirements for a multi-step task, before touching code

• SKILL.md.md
• plan-document-reviewer-prompt.md.md

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

• SKILL.md.md
• references/codex-tools.md.md
• references/gemini-tools.md.md

Use when executing implementation plans with independent tasks in the current session

• SKILL.md.md
• code-quality-reviewer-prompt.md.md
• implementer-prompt.md.md
• spec-reviewer-prompt.md.md

Use when you have a written implementation plan to execute in a separate session with review checkpoints

• SKILL.md.md

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• CREATION-LOG.md.md
• SKILL.md.md
• condition-based-waiting-example.ts.ts
• condition-based-waiting.md.md
• defense-in-depth.md.md
• find-polluter.sh.sh
• root-cause-tracing.md.md
• test-academic.md.md
• test-pressure-1.md.md
• test-pressure-2.md.md
• test-pressure-3.md.md

Use when creating new skills, editing existing skills, or verifying skills work before deployment

• SKILL.md.md
• anthropic-best-practices.md.md
• examples/CLAUDE_MD_TESTING.md.md
• graphviz-conventions.dot.dot
• persuasion-principles.md.md
• render-graphs.js.js
• testing-skills-with-subagents.md.md

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.

• SKILL.md.md
• scripts/frame-template.html.html
• scripts/helper.js.js
• scripts/server.cjs.cjs
• scripts/start-server.sh.sh
• scripts/stop-server.sh.sh
• spec-document-reviewer-prompt.md.md
• visual-companion.md.md