
Publisher on askill
Enforces test-driven development (TDD) by requiring a failing test before writing any code. Use when implementing any feature or bugfix.
Enforces a systematic debugging process to find root causes before attempting fixes. Use when encountering any bug, test failure, or unexpected behavior.
Executes written implementation plans in batches with sequential review checkpoints. Use when you have a written implementation plan to execute in a separate session.
Handles code review reception with technical rigor and verification before implementing suggestions. Use when receiving code review feedback, especially if it seems unclear or technically questionable...
Explores user intent, requirements, and design before implementation. Use when starting any creative work, creating features, building components, adding functionality, or modifying behavior.
Guides the completion of development work by verifying tests and presenting structured options for merge, PR, or cleanup. Use when implementation is complete and you need to decide how to integrate th...
Establishes skill invocation requirements at the start of any conversation. Use when starting any conversation, requiring Skill tool invocation before any response.
Handles code review reception with technical rigor and verification before implementing suggestions. Use when receiving code review feedback, especially if it seems unclear or technically questionable...
Enforces test-driven development (TDD) by requiring a failing test before writing any code. Use when implementing any feature or bugfix.
Enforces a systematic debugging process to find root causes before attempting fixes. Use when encountering any bug, test failure, or unexpected behavior.
Explores user intent, requirements, and design before implementation. Use when starting any creative work, creating features, building components, adding functionality, or modifying behavior.