decision-trace

Installation
SKILL.md

Decision Trace

Treat a claimed decision as a lineage from its source to delivery artifacts. Prove the decision and each handoff without judging whether code satisfies it. When the user asks whether the decision was implemented correctly, finish this trace before invoking acceptance-review with its handoff.

1. Frame the claim and cutoff

Rewrite the claimed decision as one or more exact behaviors without strengthening it. Split behaviors whose lineage can differ. Record the source scope, relevant repositories, and the artifact date or revision that defines the trace cutoff. Use the available primary source regardless of provider.

Complete when: every claimed behavior, the source scope, and the trace cutoff are explicit, with unavailable inputs recorded as gaps.

2. Classify the source record

Read the relevant primary-source span from the first claim through its latest qualification, objection, resolution, or superseding statement. Quote only decisive words; attach the speaker, date, and a precise locator. Label each non-quote as paraphrase or inference.

Classify each claim:

Installs
2
Repository
mintuz/skills
GitHub Stars
22
First Seen
Jul 23, 2026
decision-trace — mintuz/skills