pi-superpowers

Use before any creative work - creating features, building components, adding functionality, or modifying behavior.

Use when implementing new features or applications, or starting complex multi-step tasks that may benefit from structured workflows like brainstorming, TDD, or debugging. NOT for simple questions or straightforward operations.

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

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Use when executing implementation plans with independent tasks in the current session

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in <project_root>/.worktrees

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

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

Use when implementing any feature or bugfix, before writing implementation code

Use when creating new skills, editing existing skills, or verifying skills work before deployment