Claude Skills by TeamManagementPlugin

Systematic debugging — a four-phase root-cause methodology, boundary instrumentation for multi-component systems, the 3-fix escalation rule, and a verification gate to run before claiming anything is fixed. Use on any test failure, production bug, build failure, performance regression, or integration glitch, and especially before saying work is done. Triggers on stack traces, intermittent failures, "should work", and the third failed fix attempt on the same bug.

How to receive code review as technical evaluation rather than social performance — verify claims against the codebase before implementing, push back with evidence, and drop the performative agreement. Use when responding to a human reviewer, a PR comment, or another AI reviewer, and when deciding whether a suggestion is actually right for this codebase. Triggers on review feedback, "you're absolutely right", scope-expanding suggestions, and hallucinated file paths from external reviewers.

Test-driven development discipline — when TDD applies, when forcing it is wrong, and the RED-GREEN-REFACTOR loop with an explicit "watch it fail" step. Use when writing or reviewing tests, fixing a bug, changing behaviour, or deciding whether a change needs a test at all. Triggers on bug fixes, new validation or contracts, refactoring, and any moment the temptation is to write the test after the code.