Reviewing an opposing party's post-trial brief to identify mischaracterizations, legal errors, and factual vulnerabilities for use in preparing a response brief.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill identify-errors-and-vulnerabilities-in-counterpartys-post --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Identify Errors And Vulnerabilities In Counterpartys Post?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-identify-errors-and-vulnerabilities-in-counterpart)More formats (shields.io, HTML) on the badges page.
---
name: identify-errors-counterparty-post-trial-brief
task_id: intellectual-property/identify-errors-and-vulnerabilities-in-counterpartys-post
description: Reviewing an opposing party's post-trial brief to identify mischaracterizations, legal errors, and factual vulnerabilities for use in preparing a response brief.
activates_for: [planner, solver, checker]
---
# Skill: Identify Errors and Vulnerabilities in Counterparty's Post-Trial Brief
## 1. Subject-matter triage
Treat the post-trial brief as the target document and the trial record, claim-construction materials, prosecution-history materials, expert reports, demonstratives, and damages support as the source set for verification.
Build a source hierarchy before analyzing:
1. Governing court-adopted claim constructions and other controlling legal rulings
2. Trial testimony and admitted exhibits
3. Prosecution history and related intrinsic materials
4. Expert opinions and damages materials
5. The opposing brief's characterizations and inferences
When the brief addresses multiple doctrines, theories, witnesses, or damages inputs, enumerate them first and analyze each separately rather than collapsing them into one generalized pass.
## 2. Failure modes the skill is correcting
- Reading the brief as advocacy instead of testing every assertion against the underlying record
- Missing where the brief overstates, understates, or omits record facts that matter to liability, damages, or remedies
- Accepting legal framing that is inconsistent with controlling constructions, prosecution-history limits, or governing damages law
- Overlooking witness misquotes, selective paraphrases, or inferences presented as testimony
- Failing to separate weak rhetoric from issues that can actually move the outcome
## 3. Legal frameworks / domain conventions that apply
- A post-trial brief must track the trial record; a statement about what a witness said or what an exhibit shows is vulnerable if the cited material does not support it.
- Claim scope arguments must conform to the court's adopted constructions and any intrinsic-history limits; a brief that reintroduces rejected scope should be flagged.
- Damages arguments should be checked against the applicable reasonable-royalty framework, the stated royalty base and rate logic, and any governing apportionment requirement.
- Comparable-license arguments should be tested for technological comparability, economic comparability, litigation pressure, timing, licensing posture, and whether the license structure distorts the royalty base.
- Prosecution-history arguments must account for amendment history, disclaimer, and estoppel; a brief that ignores intrinsic limits is legally exposed.
- Willfulness and enhanced-damages arguments must rest on the controlling state-of-mind standard and the record actually credited at trial.
- Any legal proposition used in the memo should be tied to controlling authority by name or section, or to the governing court ruling as reflected in the source materials.
## 4. Analytical scaffolds
1. Create an issue map of the opposing brief by section and sub-argument.
2. For each issue, identify the precise record citations the brief relies on.
3. Verify whether each cited source actually supports the proposition stated in the brief.
4. Compare each substantive argument to the controlling claim constructions and intrinsic record.
5. For each damages assertion, identify the theory, inputs, comparables, and any apportionment logic.
6. For each cited license or damages comparator, test comparability in technology, economics, and context; flag any litigation-driven or structurally distorted comparator.
7. For each willfulness or enhanced-damages point, test the record predicate and the governing legal standard.
8. For each prosecution-history point, test whether the brief omits an amendment, disclaimer, or estoppel limit.
9. Rank each issue by legal strength and likely impact on the response brief or post-trial outcome.
10. When possible, pair each issue with a concise counter-position and the source material needed to support it.
For every issue entry, close the analysis by stating:
- the scale of the problem using a record-based measure from the source set,
- the related authority or source document that interacts with it,
- and the consequence for the client's response strategy or merits position.
## 5. Vertical / structural / temporal relationships
When the brief relies on earlier events to support later conclusions, trace the sequence carefully:
- pre-suit conduct
- claim construction
- trial testimony
- post-trial argument
- requested remedy
Check whether the brief improperly imports later-developed theories into earlier record events, or treats tentative testimony as settled fact.
If the source set contains multiple witnesses, multiple licenses, or multiple accused features, assess each one on its own terms before comparing them. Do not assume a representative sample resolves the whole issue.
## 6. Output structure conventions
Produce an issue-spotting memo organized by the opposing brief's major sections, not by a generic checklist.
Use a uniform entry format for each issue:
- Brief section and page reference
- Severity: Critical / High / Medium / Low
- Issue statement
- Why it is vulnerable, tied to the record and controlling law
- Best counter-point or rebuttal posture
- Record citation(s) to verify
- Consequence for the response brief or remedy request
Keep the memo concise but complete. Group closely related issues where they share the same record source and legal theory; otherwise keep them separate.
End with a short Recommended Actions block that assigns each next step to an appropriate role and timing tied to briefing deadlines or the next litigation milestone.
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!