nobody-plans-for-pi

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

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

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

Use when implementation is complete and all tests pass — guides completion by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions — requires technical rigor and verification, not performative agreement

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

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

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

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

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