Index of every page on this site: llms.txt
All skills
obra avatar

obra/superpowers

An agentic skills framework & software development methodology that works.

main Updated 2 weeks agoGitHub
README badge for obra/superpowers

Repository statistics

  • Indexed skills

    15

  • Skill groups

    1

  • GitHub stars

    322,972

  • Forks

    28,675

15 total

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

Updated

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

Updated

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

Updated

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

Updated

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Updated

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

Updated

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

Updated

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

Updated

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

Updated

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

Updated

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Updated

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

Updated

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Updated

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

Updated

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

Updated

The badge links readers to this page. It shows the skilld mark and no counts, and it follows the reader's light or dark GitHub theme.

<a href="https://skilld.dev/gh/obra/superpowers"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://skilld.dev/b/obra/superpowers?theme=dark"> <source media="(prefers-color-scheme: light)" srcset="https://skilld.dev/b/obra/superpowers?theme=light"> <img alt="Skill repository on skilld.dev" src="https://skilld.dev/b/obra/superpowers?theme=light"> </picture> </a>