HashWarlock/nobody-plans-for-pi

nobody-brainstorms

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

nobody-debugs

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

nobody-executes-plans

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

nobody-finishes-a-development-branch

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

nobody-receives-code-review

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

nobody-requests-code-review

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

nobody-uses-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans

nobody-uses-tdd

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

nobody-verifies-before-completion

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

nobody-writes-plans

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

nobody-writes-skills

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

using-plans-for-nobody

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