investigation-mode
npx machina-cli add skill faulkdev/github-copilot-superpowers/investigation-mode --openclawInvestigation Mode [DEPRECATED]
â ď¸ This skill has been superseded by systematic-debugging.
This file is maintained for backward compatibility. All new work should reference the promoted systematic-debugging skill instead.
Why the migration?
The systematic-debugging skill (promoted from OBRA) provides:
- 4-phase workflow with explicit procedures
- Detailed Phase 1-4 with checkpoints
- Clear anti-patterns and red flags
- Real-world debugging impact metrics
Quick mapping
| Old (this skill) | New (systematic-debugging) |
|---|---|
| "2+ failures" trigger | "ANY unclear error" entry |
| PAUSE + investigate | Phase 1: Root Cause Investigation |
| Research phase | Phase 2: Pattern Analysis |
| Direction approval flow | Phase 3: Hypothesis & Testing |
| Test first requirement | Phase 4, Step 1: Create test case |
Migration
For ongoing projects: Update references to use systematic-debugging skill.
For new work: Start with systematic-debugging (5-phase workflow).
Source
git clone https://github.com/faulkdev/github-copilot-superpowers/blob/integrate-obra-superpowers/.github/skills/investigation-mode/SKILL.mdView on GitHub Overview
Investigation-mode offered a structured debugging workflow with a four-phase process and explicit checkpoints. It is superseded by systematic-debugging, and ongoing work should migrate to the promoted five-phase workflow. This legacy skill remains for backward compatibility with migration guidance clearly outlined in its SKILL.md.
How This Skill Works
Investigation-mode used a four-phase workflow with explicit procedures and checkpoints, guiding practitioners through triggers such as unclear errors or multiple failures. It moved through Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Test Case creation. For new work, use systematic-debugging with its five-phase workflow.
When to Use It
- When you encounter an unclear error and need root-cause investigation
- When there are 2+ failures in a component and you pause to investigate (legacy trigger mapped to ANY unclear error in the new workflow)
- When you want to perform pattern analysis to spot recurring issues
- When you need a direction approval flow during debugging
- When you want to create a test case to reproduce or lock in a fix
Quick Start
- Step 1: Acknowledge that investigation-mode is deprecated and plan migration to systematic-debugging
- Step 2: For ongoing work, update references to the new skill and align with its 5-phase workflow
- Step 3: Review the linked systematic-debugging SKILL.md and begin using it for new work
Best Practices
- Prioritize migrating ongoing projects to systematic-debugging for consistency
- Document explicit phase checkpoints and anti-patterns to avoid red flags
- Map legacy triggers to the modern ANY unclear error entry in the new workflow
- Capture real-world debugging impact metrics to justify fixes
- Adopt the five-phase workflow for all new work
Example Use Cases
- Legacy incident where a flaky API produced unclear errors; migration to systematic-debugging is recommended
- An ongoing project updated its references from investigation-mode to systematic-debugging
- A team used the 2+ failures trigger historically; now aligns with ANY unclear error entry in the new workflow
- Pattern analysis revealed a root cause affecting multiple modules after applying the investigation-mode approach
- A regression test case was created to reproduce the bug and validate the fix
