What problem does it solve? Defect fixes often ship without verified reproduction, scoped authority, or runtime evidence, causing superseded PRs, unbounded changes, and unproven claims. This Skill enforces a receipt-driven development (RDD) workflow that gates every defect fix on approval, reproduction, bounded change budgets, and candidate-bound proof. ## Core Features & Use Cases - Authority and kill-switch gating: Checks the user-owned RDD mode, requires an approved issue and clean main reproduction, and audits existing PRs for supersession or conflict before any work begins. - Bounded, evidence-backed fixes: Groups work by causal invariant, enforces a 400-line change budget with chain or exception handling, and requires black-box bench journeys or real runtime E2E proof per operator flow. - Independent validation and structured output: Requires read-only candidate validation before publication and returns a structured verdict covering receipts, lineage, rollback, tests, and unresolved maintainer decisions. - Use Case: A maintainer asks you to fix a CLI defect. The Skill verifies the issue is approved, reproduces the bug on main, isolates a worktree, adds failing tests, keeps the diff under budget, records per-flow runtime evidence, and delivers a validated verdict. ## Quick Start Ask the assistant to guide a defect fix using the RDD workflow for an approved issue, starting with the kill-switch and reproduction checks.
