-
Notifications
You must be signed in to change notification settings - Fork 0
task(skills): replace curated systematic-debugging with groundwork-native original #93
Description
Parent: #44
Summary
Groundwork curates systematic-debugging from obra/superpowers (pinned at rev e4a2375). This skill enforces root-cause investigation before fix attempts. The integration review surfaced structural problems:
- One-directional composition.
using-groundworkreferencessystematic-debuggingin its Execute stage, but the debugging skill references only superpowers skills (superpowers:test-driven-development,superpowers:verification-before-completion), not groundwork equivalents. superpowers:prefix mismatch. Internal references use the prefixed name, but skills are installed without prefix.- Overlap with TDD not delineated. The skill's Phase 4 ("Create Failing Test Case") overlaps with TDD's debugging integration section. Neither skill defines which owns the debugging-to-test handoff.
- Vocabulary drift. "Your human partner" convention, superpowers-specific framing.
- Companion files reference superpowers ecosystem.
root-cause-tracing.md,defense-in-depth.md, andcondition-based-waiting.mdare co-located but may contain superpowers-specific assumptions. - No pipeline awareness. The skill doesn't know about
bddbehavior contracts,plandesign documents, orbegin/landsession lifecycle — all of which provide context that improves debugging.
Methodology
The existing superpowers skill is the primary source material, not just prior art. It contains battle-tested patterns forged through real use — the four-phase investigation model (Root Cause → Pattern Analysis → Hypothesis Testing → Implementation), the "3+ fixes failed = question the architecture" escalation rule, the evidence-gathering-before-fixing discipline, and the anti-rationalization patterns. These are extracted and preserved.
The tools serve distinct roles in the process:
- The superpowers skill itself: primary input. Extract the core investigation model, escalation rules, and diagnostic patterns. Also evaluate the companion files (
root-cause-tracing.md,defense-in-depth.md,condition-based-waiting.md) for portable know-how. ground: verify which patterns are load-bearing vs. inherited from the superpowers context. Separate bedrock discipline (root cause before fixes, evidence gathering, the 3-fix escalation rule) from context-specific framing ("your human partner" signals,superpowers:references).research: fill gaps — particularly the debugging-to-test handoff with the TDD replacement (task(skills): replace curated test-driven-development with groundwork-native original #91), and how behavior contracts frombddcan inform root-cause investigation.skill-creator: build, evaluate, and iterate the new skill.
Scope
- Extract core investigation patterns from the existing superpowers
systematic-debuggingskill and its companion files - Use
groundto verify which patterns are load-bearing vs. context-inherited - Use
researchto fill identified gaps (TDD handoff, BDD-aware debugging) - Use
skill-creatorto build and evaluate the replacement - The replacement skill should compose with TDD replacement (task(skills): replace curated test-driven-development with groundwork-native original #91) for the test-first debugging flow, and with
bddfor behavior-contract-aware debugging - Remove the
obra/superpowersdependency fromagents.tomlonce the replacement is live
Acceptance criteria
- New skill exists at
skills/<name>/SKILL.mdas a groundwork-native original (name determined during creation viaground) - Skill created using
skill-creatorwith evaluation loop - Core patterns from the superpowers original are preserved: four-phase investigation model, root-cause-before-fixes discipline, evidence gathering, 3-fix architectural escalation rule
- Cross-references integrate with groundwork pipeline: TDD replacement (task(skills): replace curated test-driven-development with groundwork-native original #91) for test-first debugging,
bddfor behavior contract context, verification replacement (task(skills): replace curated verification-before-completion with groundwork-native original #94) for fix verification - Debugging-to-test handoff is explicit — no overlap ambiguity with the TDD skill
-
using-groundwork,WORKFLOW.md, and pipeline contract updated to reference the new skill name -
systematic_debuggingentry removed fromagents.toml - Installed copies removed from
.claude/skills/and.codex/skills/ - Companion reference files (
root-cause-tracing.md,defense-in-depth.md,condition-based-waiting.md) evaluated and migrated or superseded
Dependencies
Depends on: #44 (evaluation verdict drives this work)
Prior art
- The superpowers original provides the four-phase investigation model and the architectural escalation rule
third-forceskill: structural friction resolution shares the "stop before routing around" discipline with debugging's "stop before guessing"