Test Driven Development

Writing Plans

obra

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

Verification Before Completion

obra

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

Using Superpowers

obra

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

Using Git Worktrees

obra

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

Requesting Code Review

obra

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

Receiving Code Review

obra

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