1 of 15

otherusing superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions2026-10-12

otherwriting skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment2026-10-12

otherreceiving code reviewUse 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 implementation2026-10-12

otherdispatching parallel agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies2026-10-12

otherfinishing a development branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work2026-10-12

othersubagent driven developmentUse when executing implementation plans with independent tasks in the current session2026-10-12

otherbrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.2026-10-10

workflow1brainstormingexplore intent, requirements and design out loud before any creative work, so the building starts from the right place.workflowplanningprocess2026-09-09

workflowexecuting planswork through a written plan in a fresh session, with review checkpoints so drift gets caught early.workflowprocessagents2026-09-09

coderequesting code reviewhow to ask for a review that actually checks the work against what was asked, and what to hand the reviewer.codeprocessworkflow2026-09-09

code3systematic debugginga method for bugs and failing tests: reproduce, isolate, understand, and only then propose a fix.debuggingcodeprocess2026-09-09

codetest-driven developmentwrite the failing test first, then the code that makes it pass: the discipline, spelled out for a model.tddtestingcode2026-09-09

codeusing git worktreesgive a piece of work its own checkout so it can't disturb the one you're in, with git worktree as the fallback.codeworkflowengineering2026-09-09

codeverification before completionrun the checks and read the output before saying anything is done, fixed or passing. evidence before claims.testingprocessworkflow2026-09-09

workflowwriting plansturn a spec into a plan another engineer could follow cold: bite-sized tasks, the files to touch, how to test each one.planningworkflowprocess2026-09-09

other

using superpowers

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

/skills/obra-using-superpowers

written byJesse Vincent

brought bykt

last tended2026-10-12

in the folderobra/superpowers · skills/using-superpowers

open its own page