diff options
| author | Jesse Vincent <jesse@primeradiant.com> | 2026-07-05 10:50:42 -0700 |
|---|---|---|
| committer | Jesse Vincent <jesse@primeradiant.com> | 2026-07-05 10:50:42 -0700 |
| commit | 67f513f3468ad2f7dd2d05ed95ce70fce3156e1d (patch) | |
| tree | ea353a83decc107f085e8e6dc0ca4f0863576f69 | |
| parent | 9158aa3eed2c81e89c5f4b3ceb545d0f53c27bee (diff) | |
refactor(skills): fold systematic-debugging Related-skills block into Phase 4integration-section-cleanup
Same treatment as subagent-driven-development and executing-plans: the
test-driven-development entry duplicated the reference already at Phase 4
Step 1, and the verification-before-completion entry was a sole carrier —
it moves to its point of use in Phase 4 Step 3 (Verify Fix). Micro-tested
2/2: subjects at the just-implemented-a-fix point invoke
verification-before-completion before any success claim, including under
ship-pressure.
| -rw-r--r-- | skills/systematic-debugging/SKILL.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/skills/systematic-debugging/SKILL.md b/skills/systematic-debugging/SKILL.md index b0eca38..1c0be57 100644 --- a/skills/systematic-debugging/SKILL.md +++ b/skills/systematic-debugging/SKILL.md @@ -188,6 +188,7 @@ You MUST complete each phase before proceeding to the next. - Test passes now? - No other tests broken? - Issue actually resolved? + - Use the `superpowers:verification-before-completion` skill before claiming success 4. **If Fix Doesn't Work** - STOP @@ -283,10 +284,6 @@ These techniques are part of systematic debugging and available in this director - **`defense-in-depth.md`** - Add validation at multiple layers after finding root cause - **`condition-based-waiting.md`** - Replace arbitrary timeouts with condition polling -**Related skills:** -- **superpowers:test-driven-development** - For creating failing test case (Phase 4, Step 1) -- **superpowers:verification-before-completion** - Verify fix worked before claiming success - ## Real-World Impact From debugging sessions: |
