What problem does it solve? Teams often claim a decision was made in a meeting or that work was delivered, but verifying that claim requires manually digging through transcripts, specs, issues, PRs, and commits. This Skill structures that verification by classifying the source claim, grading every handoff in the delivery lineage, and preparing a clean contract for acceptance review without prematurely judging implementation correctness. ## Core Features & Use Cases - Source Classification: Classifies each claim as decision, proposal, disagreement, or unknown with a confidence grade, exact quotes, locators, and named evidence gaps. - Delivery Lineage Grading: Grades every handoff (explicit, inferred, changed, missing) from source statement through decision records, specs, issues, PRs, and commits, detecting supersession and authority shifts. - Acceptance Handoff Preparation: Selects the authoritative requirement artifact and implementation subject for a downstream acceptance-review, flagging provisional handoffs and unresolved authority gaps. - Use Case: A status document claims a feature was delivered. Use this Skill to verify the claim against PRs and commits dated after the document, trace the requirement back to the original meeting decision, and produce a trace report before any acceptance verdict. ## Quick Start Use $decision-trace to verify whether the decision claimed in this meeting transcript was actually delivered through our specs, issues, and merged PRs.
