> browse/registry

> 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

> subagent-driven-development

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

> 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

> requesting-code-review

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

> systematic-debugging

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

> executing-plans

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