Disclosure List Andrew Bird logo

Disclosure List Andrew Bird

Organization
lawve-ai
disclosure-list-andrew-bird

Works out which documents you have to hand over to the other side in a civil case in England & Wales, and builds the formal list. The part it gets right that trips people up is which disclosure regime applies — Practice Direction 57AD (the Disclosure Pilot, now permanent in the Business and Property Courts, with its Models A–E) or standard disclosure under CPR Part 31 everywhere else. It picks the regime, chooses a Model per issue, structures the Disclosure Review Document, and drafts the disclosure certificate for the party to sign personally. Built for litigation juniors, in-house counsel, and small teams without a precedent bank. Use when the user says 'disclosure list', 'PD 57AD', 'Model C', 'extended disclosure', 'List of Documents', 'N265', or needs to work out what must be disclosed.

Overview

Publisherlawve-ai
Repositoryawesome-legal-skills
Skill namedisclosure-list-andrew-bird
Stars
854
Forks
111
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by lawve-ai on GitHub. Read the source before you install it.

Installation

Install the Disclosure List Andrew Bird AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/disclosure-list-andrew-bird
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git /tmp/awesome-legal-skills
mkdir -p .claude/skills
cp -r /tmp/awesome-legal-skills/skills/disclosure-list-andrew-bird .claude/skills/disclosure-list-andrew-bird
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Disclosure List Andrew Bird in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Disclosure List Andrew Bird on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Disclosure List Andrew Bird is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/disclosure-list

  1. Identify the regime — PD 57AD (Business and Property Courts: Commercial Court, Chancery Division, TCC, Circuit Commercial, IP, Financial List) or CPR Part 31 (everywhere else, including most county court multi-track cases).
  2. Under PD 57AD: select the appropriate Extended Disclosure Model(s) (A–E) per issue. Initial Disclosure is also required.
  3. Under CPR 31: apply "standard disclosure" (CPR 31.6) — documents on which a party relies, plus documents that adversely affect own case / support another party's case / are required by a relevant practice direction.
  4. Build the List of Documents (N265 form under CPR; Disclosure Review Document under PD 57AD).
  5. Apply privilege screening before disclosure.

Disclosure list

Which regime?

Court / DivisionRegime
Business and Property Courts (Commercial, Chancery, TCC, Circuit Commercial, IP, Financial List)PD 57AD (Disclosure Pilot — now permanent)
Other High Court divisions, County Court, fast track and multi-trackCPR Part 31
Small claims trackCPR 27.4 (limited disclosure on directions)
Family proceedingsFPR — separate regime not covered here

PD 57AD — Extended Disclosure Models

After Initial Disclosure (limited — documents relied on plus those required for the other party to understand the case), the parties agree or the court orders Extended Disclosure by issue, using one or more of:

ModelWhat it requires
ADisclosure confined to known adverse documents (no further search).
BLimited disclosure — documents necessary to enable other parties to understand the case being advanced. No proactive search beyond what was done for Initial Disclosure.
CRequest-based search — disclosure of specific documents or narrow classes specified by request. The narrowest "real search" model.
DNarrow search-based disclosure — search for documents likely to be relevant + adverse documents found. The PD 57AD equivalent of standard disclosure.
EWide search — like Model D but including the train-of-enquiry approach (Peruvian Guano style). Available only where necessary to fairly resolve issues, generally where strong reasons.

Selection happens via the Disclosure Review Document (DRD) — a structured negotiation document parties complete and exchange.

CPR Part 31 — standard disclosure

Disclose:

  • Documents on which the party relies (CPR 31.6(a)).
  • Documents which adversely affect own case, adversely affect another party's case, or support another party's case (CPR 31.6(b)).
  • Documents the party is required to disclose by a relevant practice direction (CPR 31.6(c)).

The duty extends to documents in the party's control (in physical possession, with right to possession, or right to inspect: CPR 31.8).

Inputs

  • Court / division (drives regime).
  • Issues for disclosure (PD 57AD) or pleaded issues (CPR 31).
  • Custodians (employees, agents, advisers).
  • Data sources (email, file shares, document management, messaging apps — including WhatsApp / Signal, dataroom platforms).
  • Date range.
  • Privilege scope (advice privilege, litigation privilege, WP, common-interest).
  • Confidentiality (commercially sensitive, regulatory, third-party).
  • Foreign data protection (GDPR — Article 6/49 lawful basis for transfer).

Workflow

Step 1 — Regime check

B&P Courts → PD 57AD. Otherwise CPR 31.

Step 2 — Initial Disclosure (PD 57AD)

Each party serves with Statements of Case: documents relied on + those required for other parties to understand. List of Issues for Disclosure follows in the DRD.

Step 3 — Issues for disclosure (PD 57AD only)

A focused list — not the same as pleaded issues. Should be issues that disclosure will actually inform.

Step 4 — Model selection per issue (PD 57AD)

Each issue gets a model. Default to Model C (request-based) where possible; Model D for broader issues; Model E only in exceptional cases.

Step 5 — Custodian / data-source mapping

Who held the relevant documents; where the data lives; what platforms (Outlook / Gmail / Teams / Slack / WhatsApp / dataroom / paper).

Step 6 — Search methodology

  • Date ranges.
  • Custodians.
  • Data sources.
  • Keywords (PD 57AD requires keyword lists and dedupe approach to be agreed).
  • Use of technology-assisted review (TAR / predictive coding) — disclose use in the DRD.

Step 7 — Privilege review

  • Advice privilege: communications between solicitor and client for the purpose of legal advice.
  • Litigation privilege: communications with third parties (witnesses, experts) where the dominant purpose is for litigation reasonably contemplated.
  • WP: settlement correspondence.
  • Common interest: shared legal interest with a third party (insurer, co-defendant).

Privileged documents are listed by description, not produced. Redaction of privileged parts is permissible.

Step 8 — List of Documents

CPR 31 — N265 List of Documents (or equivalent):

Three parts:

  • Part 1: documents in control, available for inspection.
  • Part 2: documents in control, but right or duty to withhold from inspection (privilege).
  • Part 3: documents that have been but are no longer in control (when and how parted with).

Plus the Disclosure Statement (signed personally — CPR 31.10) certifying the search and the duty.

PD 57AD — Disclosure Certificate

Signed by the party (not the solicitor) certifying the search complied with the order and disclosure obligations under the PD. Like the CPR 31.10 statement, any draft Disclosure Certificate the skill produces is scaffolding, not an executed certificate — carry the same DRAFT banner across, do not present the certification as made, and the party must sign it personally only once the search has actually been performed.

Output

Produce the list using the sections below. Render it as the finished List of Documents — do not echo this template back, and do not invent documents, custodians, or sources to fill a section. If a part has nothing in it, say so. Every document listed must trace to a real input the user supplied; the skill scopes and drafts the list, it does not generate the documents that go in it.

Output template (CPR 31)

List of Documents — [Case name and claim number]

Part 1: Documents in our client's control which we do not object to producing for inspection

IDDateDescriptionCustodian / source
C/1[date][description][custodian]

Part 2: Documents in our client's control which we object to producing for inspection

IDDateDescriptionGround
C/P/1[date][generic description]Legal advice privilege
C/P/2[date][description]Litigation privilege
C/P/3[date][description]Without prejudice

Part 3: Documents which were but are no longer in our client's control

DateDescriptionWhen and how parted withWhereabouts believed

Disclosure Statement (CPR 31.10)

DRAFT — NOT AN EXECUTED STATEMENT. This is scaffolding for a Disclosure Statement, not a completed one. Before it can be filed: the statement must be reviewed; the search it describes must actually have been performed; and it must be signed personally by the party under CPR 31.10. Do not file as generated. Do not present the blanks as filled, and do not assert the search was carried out — only the signing party can certify that. Render this with the banner attached and the certification text shown as wording the party must adopt for themselves, not as a statement the model is making.

I, [name], state:

  1. My address is [...]. I am [position].
  2. I have been authorised to make this disclosure statement on behalf of [party].
  3. I am familiar with the issues in this case as set out in [pleadings].
  4. I conducted a search for documents that I am required to disclose in accordance with [order / standard disclosure / agreed scope].
  5. The search covered [custodians, data sources, date range, keywords].
  6. I did not search for [excluded sources — eg paper archives older than 7 years, dormant servers] — give reasons.
  7. I certify I understand the duty to disclose and to the best of my knowledge I have carried it out.

Signed: [party — sign personally, CPR 31.10] Date: [date]

Output template (PD 57AD Disclosure Review Document, simplified)

Disclosure Review Document — [Case]

Section 1A: Initial Disclosure

[Complete — list of documents already provided.]

Section 1B: Issues for Disclosure

No.IssueProposed ModelReasons
1[issue 1]C[...]
2[issue 2]D[...]

Section 2: Custodians, sources, date range, keywords

[Table — agreed or proposed per issue.]

Section 3: Technology

  • Use of TAR / predictive coding: [yes/no, model]
  • De-duplication, near-duplication, threading: [methodology]

Section 4: Cost estimate

[Per CPR Part 47 / PD 57AD requirement.]

Markers

  • [REGIME — confirm court division]
  • [PRIVILEGE — flagged but not yet reviewed]
  • [GDPR — cross-border transfer requires Art 6/49 basis]
  • [SME VERIFY — Model selection per issue]

What this skill does not do

  • Run the search. It scopes and lists; the search itself happens outside the model and must actually be performed before any list or statement is certified.
  • Decide privilege. It flags candidates by description; counsel reviews every flagged document and makes the privilege call.
  • Certify anything. The Disclosure Statement (CPR 31.10) and Disclosure Certificate (PD 57AD) are signed personally by the party — the model drafts scaffolding, it does not make the certification.
  • Cover Scottish / NI procedure (Commission and Diligence; Schedule 1 RCS).
  • Give legal advice. This is a drafting aid that produces a draft for solicitor review. Nothing it generates should be filed as generated — verify the scope, the search, and the privilege calls with counsel before relying on or serving any output.

Frequently asked questions

What does the Disclosure List Andrew Bird AI skill do?

Works out which documents you have to hand over to the other side in a civil case in England & Wales, and builds the formal list. The part it gets right that trips people up is which disclosure regime applies — Practice Direction 57AD (the Disclosure Pilot, now permanent in the Business and Property Courts, with its Models A–E) or standard disclosure under CPR Part 31 everywhere else. It picks the regime, chooses a Model per issue, structures the Disclosure Review Document, and drafts the disclosure certificate for the party to sign personally. Built for litigation juniors, in-house counsel...

Why use Disclosure List Andrew Bird on TypingMind?

Because you install it once and use it with any model. Disclosure List Andrew Bird is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Disclosure List Andrew Bird in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/disclosure-list-andrew-bird. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Disclosure List Andrew Bird?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Disclosure List Andrew Bird?

As many as you like. As long as a model supports skills, you can use Disclosure List Andrew Bird with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Disclosure List Andrew Bird AI skill free?

It is published on GitHub by lawve-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇