メニュー
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Trace the current state of a UK Act including in-force amendments AND any pending bills that would amend it. Use whenever the user asks "is <Act> current", "what's the latest version of <Act>", "have any bills amended this", "what's pending for <Act>", or "what changes are proposed to <Act>". Statutes are living documents — a citation without amendment-status risks citing repealed or superseded text.
Trace the parliamentary journey of a UK bill — debates, key contributions, and divisions. Use whenever the user asks "how did the <bill> progress", "who spoke against the <bill>", "what was the vote on <bill>", "show me the Lords debates on <bill>", or "trace the <bill> through Parliament". The skill assembles a chronological view from Bills API + Hansard + Votes data.
Find a UK court judgment by party names and verify its neutral citation before citing it to the user. Use whenever the user asks "find <X v Y>", "get me the citation for <case>", "what's the neutral citation for the <case name>", "is there a case called <name>", or pastes a partial case reference. This skill verifies the case exists in TNA Find Case Law BEFORE reporting the citation — prevents the "plausible-looking but wrong" citation failure that happens when an agent formats from training data.
Construct an OSCOLA citation for a UK case, statute, or Hansard reference AFTER verifying the source exists via uk-legal MCP. Use whenever the user asks to "cite <source> in OSCOLA", "give me the OSCOLA citation for", "format this as OSCOLA", or pastes a partial citation. This skill verifies first and formats second — preventing the most common citation fabrication route where an agent formats plausible-looking fields without confirming the source actually exists.
Retrieve what a named member of either House said in a specific Hansard debate. Use this skill whenever the user asks "what did <peer/MP> say about <topic>", "find <member>'s contribution to the <bill> debate", "did <name> speak on <date>", or "quote <name>'s speech on <subject>". This skill must be used for any peer-or-MP-specific Hansard query — text-searching Hansard by member name returns unrelated debates and is the most common failure mode.
Build or review an element chart — a patent claim chart (infringement, invalidity, or review) or a civil element chart for any cause of action or defence — with every cell pin-cited and gap detection as the priority output. Use when the user asks for a claim chart, element chart, proof chart, infringement or invalidity contention, element-by-element mapping, or asks "what are we missing to prove [claim]".
| name | deal-team-summary |
| description | Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence. |
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal-uk:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
The deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.
~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md → Deal team briefing (cadence, format, what the business reads)~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/deals/[code]/deal-context.md → deal lead, timelinePer ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md — what the business reads vs. what's for the file. Default tiers:
| Audience | Gets | Doesn't get |
|---|---|---|
| Board / exec sponsor | Top 3-5 material issues, price/structure impact, decision items | Category detail, green findings, process |
| Deal lead | All reds, all yellows, progress, decision items, next steps | Green finding detail |
| Working team | Everything — full findings, status by category, gaps | Nothing withheld |
Ask which tier if not obvious.
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
> This brief aggregates privileged diligence findings and inherits the sources' legal professional privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.
# [Deal code] — Diligence Brief — [date]
**Status:** [On track / Issues identified / Material findings]
**Coverage:** [X]% of VDR reviewed
## Material findings
[3-5 max. One paragraph each. What it is, why it matters to the deal, what
we're doing about it.]
## Decisions needed
- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]
— [who decides] — [by when]
## Since last brief
[What changed. New findings, findings resolved, coverage progress.]
Same as above plus:
## All open issues by category
### 🔴 Red
[Finding title + one-line — link to full finding for detail]
### 🟡 Yellow
[same]
## Progress
| Category | Docs reviewed | Coverage | Reds | Yellows | Status |
|---|---|---|---|---|---|
| [name] | [N/M] | [%] | [N] | [N] | [Complete / In progress / Blocked] |
## Gaps and follow-ups
- [Supplemental request items outstanding]
- [Questions to management]
## Next 72 hours
[What's getting reviewed, what briefings are scheduled]
Full finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.
If this is a recurring brief (per ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md cadence), lead with what changed:
Deal leads care more about movement than state. "Still 12 yellows" is less useful than "2 new yellows, 3 resolved."
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customise the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the solicitor picks.