chronology-builder-andrew-bird
Builds a litigation chronology from the disclosure bundle itself — every entry attributed to its source document, behind a CPR 31.22 implied-undertaking check, because documents disclosed in English proceedings may only be used for those proceedings. Adds a privilege screen and case-theory significance tagging, so the output is court-facing work product, not a loose timeline. Use when the user asks to build a chronology or timeline from a disclosure bundle, a matter file, or witness statements, or says 'build the chron', 'what happened when', or needs a Statement of Facts ready timeline.
npx skills add lawve-ai/awesome-legal-skills --skill chronology-builder-andrew-bird --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /chronology 1. Run the CPR 31.22 implied-undertaking check before extracting from disclosed documents. 2. Identify sources: user-provided paths, matter folder, declared sources. 3. Extract dated events, de-duplicate against sources, tag significance per case theory. 4. Output a working chronology by default; Statement-of-Facts or witness-specific variants on request. --- # Chronology — UK civil litigation ## CPR 31.22 implied-undertaking check The host workspace enforces the hard gate (matter-slug match against the proceedings reference, privilege posture). If this skill is running, that gate has already passed — this check does not replace it. The skill still performs its own check below and refuses or flags if misuse is indicated; it is not the enforcement. Before building from any document obtained through standard or extended disclosure in English / Welsh proceedings, confirm the use is permitted: > CPR 31.22(1): A party to whom a document has been disclosed may use the document only for the purpose of the proceedings in which it is disclosed, except where: > (a) the document has been read to or by the court, or referred to, at a hearing held in public; > (b) the court gives
- CPR 31.22 implied-undertaking check
- Privilege screen
- Inputs
- Workflow
- Step 1 — CPR 31.22 implied-undertaking check (above)
- Step 2 — Privilege posture choice (above)
- Step 3 — Source identification
- Step 4 — Extraction
- Step 5 — De-duplication
- Step 6 — Significance tagging (per side)
- Step 7 — Source attribution per entry
- Step 8 — Output
- Output
- Timeline
What does the chronology-builder-andrew-bird skill do?
Builds a litigation chronology from the disclosure bundle itself — every entry attributed to its source document, behind a CPR 31.22 implied-undertaking check, because documents disclosed in English proceedings may only be used for those proceedings. Adds a privilege screen and case-theory significance tagging, so the output is court-facing work product, not a loose timeline. Use when the user asks to build a chronology or timeline from a disclosure bundle, a matter file, or witness statements, or says 'build the chron', 'what happened when', or needs a Statement of Facts ready timeline.
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill chronology-builder-andrew-bird --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.