Requesting Code Review
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
slack-messaging
Use when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.
using-tmux-for-interactive-commands
Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys
browsing
Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
dispatching-parallel-agents
Dispatch subagents in parallel when there are 2+ independent problem domains (separate failures/subsystems) that can be investigated without shared state or sequential dependencies; avoid when work is tightly coupled, ambiguous, or requires main-agent decisions.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
subagent-driven-development
Execute implementation plans in the current session by dispatching one subagent per mostly independent task with two-stage review (spec compliance, then code quality); avoid for tightly coupled or ambiguous tasks.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
verification-before-completion
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
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Subagent-Driven Development
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Using Git Worktrees
Create isolated git worktrees with smart directory selection and safety verification
Writing Plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Defense-in-Depth Validation
Validate at every layer data passes through to make bugs impossible
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
receiving-code-review
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
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
verification-before-completion
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
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Root Cause Tracing
Systematically trace bugs backward through call stack to find original trigger
Systematic Debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Verification Before Completion
Run verification commands and confirm output before claiming success
Gardening Skills Wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
Pulling Updates from Skills Repository
Sync local skills repository with upstream changes from obra/superpowers-skills
Sharing Skills
Contribute skills back to upstream via branch and PR
Testing Skills With Subagents
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Writing Skills
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Collision-Zone Thinking
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Inversion Exercise
Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
Meta-Pattern Recognition
Spot patterns appearing in 3+ domains to find universal principles
Scale Game
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales
Simplification Cascades
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
When Stuck - Problem-Solving Dispatch
Dispatch to the right problem-solving technique based on how you're stuck
Preserving Productive Tensions
Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution
Brainstorming Ideas Into Designs
Interactive idea refinement using Socratic method to develop fully-formed designs
Dispatching Parallel Agents
Use multiple Claude agents to investigate and fix independent problems concurrently
Page 1 of 2 · 64 results