pi-superpowers

Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.

Use when completing tasks, implementing major features, or before merging. Covers both performing self-review and responding to external review feedback.

Use when starting feature work needing isolation or when completing a development branch — covers worktree creation, setup, and branch finishing.

Use at the start of every conversation to establish skill-driven workflows. Ensures relevant skills are loaded before any action or response.

Use when you have a spec or requirements for a multi-step task. Covers both writing implementation plans and executing them task-by-task with review checkpoints.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims