obra/superpowers

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI....

Write the test first. Watch it fail. Write minimal code to pass.

Load plan, review critically, execute all tasks, report when complete.

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Source details, install context, and public review data are available on the full page.

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.

Code review requires technical evaluation, not emotional performance.

Claiming work is complete without verification is dishonesty, not efficiency.

Writing skills IS Test-Driven Development applied to process documentation.

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for...

Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

Guide completion of development work by presenting clear options and handling chosen workflow.