What problem does it solve? Codebases accumulate business rules that are never written down, and summarizing them by hand drops edge cases and loses track of where each rule lives. This Skill reverse-engineers the implemented decision logic from a module or service into an auditable rules specification where every rule cites exact code locations and omissions are explicitly accounted for. ## Core Features & Use Cases - Provenance-bound rule extraction: Each rule is written as a testable EARS or Given-When-Then statement bound to exact file:line citations, with quoted load-bearing code spans. - Decision-logic rendering: Every rule is rendered as an ASCII flowchart plus provenance-annotated pseudo-code covering each branch and edge case, with no invented edges. - Loss ledger and coverage gating: A companion ledger records decision-site coverage, preserved-versus-abstracted content, omissions, and a human spot-check checklist. - Cross-referencing: Rules are optionally linked to requirement IDs and execution-trace spans (OTel GenAI / OpenInference) to distinguish live logic from dead code. - Use Case: Point it at a promo-validation service and receive a rules spec showing each guard condition, its rejection outcome, and its source lines, plus a ledger flagging any uninspected callers. ## Quick Start Extract the business rules from the payment validation module into a traceable spec with a coverage ledger.
