Traces how a statutory provision reached its current form — prior versions, amendments, and the reasons for each change — using only sourced material, and keeps an amending act's own stated purpose, a court's later characterisation of that purpose, and this analysis's own inference clearly distinguished as different categories of evidence. Use this whenever a user needs a provision's legislative history traced — including phrasings like "trace how this section reached its current form", "what...
Scanned 9/4/2026
Install to Claude Code
npx -y skills add Cancellationperiplocagraeca503/legal-ai-skills --skill legislative-history-analyst --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Legislative History Analyst?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cancellationperiplocagraeca503-legislative-history-analyst)More formats (shields.io, HTML) on the badges page.
---
name: legislative-history-analyst
description: Traces how a statutory provision reached its current form — prior versions, amendments, and the reasons for each change — using only sourced material, and keeps an amending act's own stated purpose, a court's later characterisation of that purpose, and this analysis's own inference clearly distinguished as different categories of evidence. Use this whenever a user needs a provision's legislative history traced — including phrasings like "trace how this section reached its current form", "what did this amendment actually change and why", "does the legislative history support reading this provision narrowly", or "was this always the rule or was it added later". Fires for any statutory provision whose history needs tracing, in any jurisdiction — but says plainly when it cannot trace history without sources, rather than reconstructing one from memory.
---
# Legislative History Analyst
## What this does
Traces the history of a statutory provision — its prior versions, each amendment, and the reasons given for each change — using only material actually sourced this session or supplied by the user. Legislative history is exactly the kind of granular factual claim, bill numbers, amendment dates, specific debate quotes, that is easy to produce a convincing-sounding fabrication of; this skill treats every element of the history as something requiring a real source, and says plainly when it cannot trace history at all rather than reconstructing a plausible-sounding account from memory.
## Before you start
**The specific provision and jurisdiction.** Blocking.
**Whether research tools or sources are available this session, or whether the user is supplying historical material.** If neither, say plainly that legislative history cannot be traced without sources, and do not produce an account built from memory. This is the single most important gate in this skill.
Not blocking, ask once and proceed on a reasonable default without it: **how far back the history needs to go** — the original enactment, or a specific set of more recent amendments.
## Method
**1. Confirm the provision and its current text precisely, sourced or supplied.** Do not start from a remembered version of the text.
**2. Identify each prior version or amendment only from sourced material.** State the enactment date, the amending instrument, and precisely what changed in the text between versions — shown as an actual textual comparison, not merely asserted to have changed.
**3. For the reasons behind each change, cite only sourced material** — a statement of objects and reasons, a committee report, a legislative debate record. Do not infer or invent a legislative purpose that is not actually stated in a sourced document.
**4. Keep three categories of evidence for intent clearly distinguished at every point**: the amending act's own stated purpose, a court's later characterisation of that purpose, and this analysis's own inference from the material. Conflating these is one of the most common errors in this kind of analysis, and the output should never let a reader mistake one for another.
**5. Note where the history is genuinely unclear or contested** — conflicting statements about purpose, or gaps in the available record — rather than picking one narrative and presenting it as settled.
**6. Trace amendments in strict chronological order**, and flag explicitly any gap where a version's text is not available or sourced.
**7. Where the user wants the history connected to a current interpretive question, keep the historical account and the interpretive argument visibly separate.** The history is evidence; the interpretation is a conclusion drawn from it, and blending the two overstates what the history alone actually establishes.
## Output
**1. Header.** Provision, jurisdiction, current text (sourced), date, sourcing mode.
**2. Chronological history.** Each version, its amending instrument, date, and what changed, shown as a textual comparison.
**3. Stated reasons for change.** Per amendment, sourced and attributed to its specific source type — statement of objects and reasons, committee report, or debate record.
**4. Gaps and uncertainty.** Any version or reason not sourced, flagged explicitly rather than smoothed over.
**5. Interpretive relevance**, if asked for, kept clearly separate from the historical account itself.
**6. Points requiring verification.** Anything not fully sourced this session.
## Do not
Do not reconstruct a plausible-sounding legislative history from memory when sources are not available. Say so plainly instead.
Do not invent a bill number, amendment date, or debate quote.
Do not conflate an amending act's stated purpose with a court's later characterisation of it, or with this analysis's own inference.
Do not present a contested historical account as settled.
Do not blend the historical account with an interpretive conclusion. Keep them visibly separate.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!