Analyze Counterparty Markup Of Tax Closing Agreement

---
name: analyze-counterparty-markup-of-tax-closing-agreement
task_id: tax/analyze-counterparty-markup-of-tax-closing-agreement
description: Analyzing a counter-markup of a tax closing agreement requires side-by-side comparison of every changed term, quantification of incremental exposure where possible, and review of scope and penalty language for legal defects — not merely a narrative summary of differences.
activates_for: [planner, solver, checker]
---

# Skill: Analyze IRS Counter-Markup of Tax Closing Agreement

## 1. Subject-matter triage

- Treat the clean draft, the IRS counter-markup, the negotiation summary, and supporting schedules as one integrated record.
- Identify whether the markup changes tax, penalty, scope, methodology, defined terms, effective date, releases, or any recharacterization item before writing analysis.
- If the record contains multiple taxable periods, entities, or issue buckets, enumerate them up front and analyze each separately; do not collapse distinct items into one pass.
- If the task is really a comparison of one draft against one counter-draft, state that explicitly and proceed issue by issue.

## 2. Failure modes the skill is correcting

- Summarizing changes narratively without a structured comparison that shows what changed, where, and why it matters.
- Missing a changed defined term that silently expands the operative scope of a penalty, release, or payment obligation.
- Ignoring how one change affects another provision, schedule, or supporting document.
- Treating tax exposure as the only consequence and omitting penalty, interest, operational, litigation, or downstream coordination effects.
- Failing to flag overbroad scope language that could waive unrelated positions or claims.
- Overlooking language that applies penalties or consequences to amounts not actually conceded or not clearly defined.
- Not assessing whether any methodology or characterization commitment creates conflict with positions in foreign or parallel proceedings.
- Providing legal conclusions without identifying the rule, statute, regulation, or doctrine that supports them.

## 3. Legal frameworks / domain conventions that apply

- **Closing agreement finality:** A closing agreement is meant to resolve only the matters actually covered; every clause should be tested for breadth against the stated issue set and the negotiation record.
- **Defined terms control:** The operative effect often turns on defined terms, not the visible business label. Trace each defined term to its use across the agreement.
- **Scope and release principles:** Release, waiver, and covenant language should be limited to the settled matters unless the source documents support broader coverage.
- **Penalty base and trigger analysis:** Penalty language must be checked for a clear base, triggering event, and amount. Ambiguous or unadmitted bases should be flagged.
- **Corresponding or correlative adjustments:** If the agreement reallocates income, deductions, or character, check whether the record supports parallel treatment for related parties or related jurisdictions.
- **Transfer-pricing and characterization commitments:** Any required method, allocation, or character commitment must be checked against positions in other proceedings and against future-year flexibility.
- **Tax authority grounding:** Tie each legal point to the governing authority the record identifies, or to the generally recognized tax authority for the issue, such as the Internal Revenue Code, Treasury regulations, IRS procedural guidance, or applicable case law.

## 4. Analytical scaffolds

- Begin with a comparison table that lists each material changed provision, the clean-draft text or concept, the counter-markup change, the practical effect, and the recommended response.
- For each issue, state:
  - the specific provision or defined term affected;
  - what changed;
  - the exposure or other impact using any figures, thresholds, periods, or categories found in the record;
  - the cross-reference to the clause, schedule, or supporting document that interacts with the change;
  - the downstream consequence for the client;
  - the legal authority or drafting principle supporting the concern;
  - the recommended counter-language or response.
- Where the documents permit, quantify incremental exposure relative to the clean draft. If a number cannot be derived, explain the directional risk and the missing inputs.
- Compare the markup against the negotiation summary to identify changes that are inconsistent with prior positions or settlement boundaries.
- If one clause broadens a release, penalty base, or methodology commitment, test whether another clause narrows it or creates a contradiction.
- Prioritize issues by practical significance and legal risk, but preserve every material change in the comparison.
- Use an ordinal severity scale defined once at the outset and apply it uniformly to each issue entry.

## 5. Vertical / structural / temporal relationships

- Read the agreement vertically: defined term → operative clause → schedule → exception → remedy.
- Read it horizontally across documents: clean draft, counter-markup, negotiation summary, and any supporting materials that explain intent or settlement range.
- Read it temporally: current execution effect, any post-signing covenant, any future-year methodology commitment, and any downstream proceeding or reporting consequence.
- Where a change affects multiple years, multiple entities, or multiple issue buckets, analyze each affected strand separately and then note the combined effect.
- If the record contains related claims or schedules, cross-check whether the markup would alter them indirectly through scope, release, or incorporation language.

## 6. Output structure conventions

- Prepare an issues memo in industry-conventional form, not a raw redline diary.
- Open with a concise executive summary and a short severity legend.
- Follow with a comparison table that surfaces every material change in plain terms.
- For each issue, use a consistent substructure:
  - Severity
  - Provision / change
  - Impact
  - Cross-reference
  - Legal analysis
  - Recommended response
- Include explicit textual markers when describing proposed edits so the reader can distinguish deletions, insertions, and substitutions even if formatting is lost in export.
- End with a Recommended Actions section that assigns the action, the responsible role, and the timing anchor tied to the negotiation or signing milestone.
- Close with an overall recommendation on whether to accept, counter, or seek further negotiation.