Superpowers
A software-development method for coding agents, packaged as 14 skills and a starting instruction that tells the agent to check for a relevant skill before acting: brainstorming a design before building, writing and executing implementation plans, test-driven development, systematic debugging, verifying before claiming completion, requesting and receiving code review, dispatching parallel sub-agents, working in isolated git worktrees, wrapping up a finished branch, and writing new skills. Aimed at developers who want an agent to follow a disciplined plan, test and review cycle.
- Testing
- Debugging
- Code review
- Git workflow
- Task planning
Source: obra/superpowers · pinned commit b36e082
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Use staged development when the decisions justify it
Design discussion, planning, implementation and review can prevent premature coding. They still need real deliverables and a host that supports the selected workflow.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
This collection fits a nontrivial code change that benefits from discussing design before committing to implementation. The README describes a progression from brainstorming and plans to implementation with tests and review, rather than treating the first coding response as completion.
When to choose something else
Do not impose a long workflow on a one-line content correction. Also do not count a generated plan or a review request as executed evidence. The value depends on following the chosen stages with actual diffs and checks, not on the number of named stages.
What to provide and what to expect
Provide the user-visible problem, repository constraints and acceptance behavior. Expect design decisions, an implementation plan, bounded changes and review evidence. Keep approval points tied to concrete artifacts so uncertainty can be resolved before expensive edits.
Tools, permissions and boundaries
Setup varies by agent host and may include plugins or hooks. Inspect the selected host instructions before installation. Workers need isolated ownership or agreed file boundaries, and running tests needs the local toolchain; workflow text grants neither access nor successful results.
The tradeoff and an alternative
A direct fix-and-check prompt is sufficient when the problem and solution are already clear. The staged approach earns its overhead when implementation choices have material consequences. Keep the plan short enough that review can verify each promised behavior against the final change.
A small acceptance exercise
Proposed exercise: fix a reproducible validation bug. Require a check that exposes the original failure, a bounded patch and a review of the resulting behavior. Reject a handoff that supplies only assurances, or reports test success without identifying the run and its result.
Source, version and what was actually read
The pinned README opening workflow and host-specific setup overview were read. Individual skills, hooks and orchestration behavior were not evaluated. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: b36e082
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.