Skip to skills
AI Craft Pad
Home/Skills/Skill Kits/Diagnose a regression and prove the fix
Curated workflows

Diagnose a regression and prove the fix

Build a clear chain from a reproduced defect to a meaningful regression test and fresh completion evidence.

How these skills work together

Record the trigger, expected behavior and observed failure. Investigate the earliest component boundary that explains the mismatch. Express the missing behavior as a test that fails for the relevant reason, implement a focused correction, then run the final checks against the actual state that will be delivered. The sequence is suggested for complementary responsibilities; it does not establish that a particular environment or integration has been tested.

Validation and boundaries

A reviewer should see the original failure, the evidence supporting the cause, the initial regression-test failure and the final passing result. Add integration, browser, public deployment or physical-device evidence when the requested outcome crosses those boundaries.

Development88/100

systematic debugging

obra/superpowers

A structured investigation workflow for a failing build, unexpected application behavior or a regression that keeps returning.

Community sourceMITEditorial review
308,765 repo stars1 text flagReview ↗
Testing & QA88/100

test driven development

obra/superpowers

A test-first workflow for turning a specific behavior requirement into an observable failing case and a focused implementation.

Community sourceMITEditorial review
308,765 repo stars1 text flagReview ↗
Testing & QA88/100

verification before completion

obra/superpowers

A completion-check workflow that ties a claim such as fixed, passing or deployed to fresh evidence from the relevant system.

Community sourceMITEditorial review
308,765 repo stars0 text flagsReview ↗