What problem does it solve?
Fixing defects in a Receipt-Driven Development (RDD) repository requires strict evidence discipline: approved issues, reproduction on main, causal invariant isolation, line budgets, and independent validation. This Skill enforces that workflow so contributors never fabricate approvals, merge conflicting authority lines, or ship unproven fixes.
Core Features & Use Cases
- RDD Mode and Gate Enforcement: Checks the user-owned RDD kill switch first, requires an approved issue and clean main reproduction, and audits existing PRs for supersession or conflict before any work begins.
- Evidence-Bound Correction: Groups work by causal invariant, inventories every operator flow with negative controls, demands truthful black-box bench journeys or real runtime E2E proof, and enforces a 400-line change budget with chain or exception handling.
- Independent Validation: Requires read-only candidate validation before publication and returns a structured output contract covering mode, invariants, flows, evidence, budget, tests, rollback, and unresolved decisions.
- Use Case: A maintainer asks the agent to fix a CLI defect in an RDD-enabled repository; the Skill walks through mode check, issue gate, worktree isolation, failing tests, candidate freeze, and read-only validation before reporting the verdict.
Quick Start
Ask the agent to fix an approved defect issue in this repository following the RDD defect workflow with full evidence and validation.