Draft Markup Of Irs Closing Agreement

---
name: draft-markup-of-irs-closing-agreement
task_id: tax/draft-markup-of-irs-closing-agreement
description: Drafting a markup of an IRS closing agreement requires identifying and revising structural and substantive issues in the draft, including penalty-waiver language, scope language, correlative adjustments, limitations-period timing, and a companion explanatory response letter to the IRS contact.
activates_for: [planner, solver, checker]
---

# Skill: Draft Markup of IRS Closing Agreement

## 1. Subject-matter triage (only if applicable)

- Confirm the closing agreement is the primary deliverable and the response letter is secondary, but still required.
- Identify whether the draft touches one issue or multiple issue clusters; if multiple parties, tax periods, entities, or adjustment types appear, separate them before revising.
- Read the draft against the support record, not in isolation, and treat inconsistencies as markup targets rather than assumptions.
- Before finalizing, verify the agreement file exists, is non-empty, and contains operative provisions; then confirm the letter file exists and is non-empty.

## 2. Failure modes the skill is correcting

- Producing only the redlined agreement and omitting the companion formal response letter.
- Relying on formatting alone for redlines, so changes are lost on export or review in plain text.
- Missing an express penalty-related term where the draft needs one, or leaving material terms to implication.
- Leaving scope language broader than the negotiated subject matter or the supporting record.
- Failing to address correlative or corresponding adjustment language when the draft reallocates items or affects related taxpayers.
- Overlooking timing risk tied to execution, processing, filing, assessment, collection, or other limitations-sensitive milestones.
- Writing comments that describe the issue but do not explain why the revision is needed.
- Drafting a letter that is vague, apologetic, or non-committal instead of issue-by-issue and action-oriented.

## 3. Legal frameworks / domain conventions that apply

- **Closing-agreement finality:** An IRS closing agreement is intended to be binding and final under the governing Internal Revenue Code provisions; review every term as if it will govern the dispute end state.
- **Express drafting for settlement terms:** Where a consequence matters, it should appear in the text itself; do not rely on side understandings or unstated assumptions.
- **Penalty treatment:** If the business deal contemplates penalty relief, the agreement should state that treatment clearly and consistently with the settlement record.
- **Scope and issue identity:** The agreement should track the actual matters being resolved under the relevant taxable years, items, and parties, and should not expand beyond them.
- **Correlative treatment:** If the draft reallocates income, deductions, credits, or similar items, check for matching downstream treatment under the related taxpayer or companion document framework.
- **Timing and limitations sensitivity:** If the deal depends on deadlines, extensions, waivers, or processing sequence, the drafting should preserve the intended timing posture and avoid accidental lapse risk.
- **Administrative correspondence convention:** The response letter should be concise, professional, and organized as a negotiation aid, not an advocacy brief.

## 4. Analytical scaffolds

- Start by inventorying the issue set and separating each distinct revision target before drafting.
- For each issue, compare the draft text to the support materials and determine whether the wording matches the negotiated result.
- Mark every substantive textual change with a robust plain-text convention, such as [DELETED: ...], [INSERTED: ...], or [REPLACED: old → new], and add a short bracketed rationale for each change.
- For each identified issue, state the severity once using a uniform ordinal scale defined up front in the deliverable commentary, then explain the drafting consequence.
- For each issue, tie the revision to the relevant clause, exhibit, schedule, or related document and explain the downstream effect on the client.
- If there is only one issue cluster, say so expressly; if there are multiple clusters, address each separately rather than combining them.
- In the response letter, mirror the markup issues in the same order, explain the requested change, and indicate the practical step needed to move toward final execution.
- Use authoritative citations where a legal proposition is stated; anchor the point in the governing Internal Revenue Code, Treasury regulation, or other cited authority appearing in the source record, or in generally recognized tax authority if none is provided.

## 5. Vertical / structural / temporal relationships (only if applicable)

- Track whether a revision affects more than one taxpayer, tax year, adjustment category, or related filing position; if so, state each relationship before drafting the fix.
- Check whether a proposed edit in one clause creates a mismatch elsewhere in the agreement, the exhibits, or the transmittal correspondence.
- Watch for sequencing issues: an agreement that must be signed before a deadline, transmitted before processing, or aligned with another filing should be redrafted to preserve that order.
- If the draft contemplates offsets, reallocations, or matching positions between related parties, ensure the correspondence reflects the same directional treatment and no hidden asymmetry remains.

## 6. Output structure conventions

- Produce two deliverables: a redlined closing agreement and a formal response letter to the IRS Appeals Officer.
- In the redlined agreement, make every substantive change visible in plain text and attach a bracketed comment explaining the reason for the revision.
- Use a clear issue-by-issue structure in the letter, with a neutral professional tone and a specific ask for each revision.
- Keep the markup and the letter aligned: each proposed textual change in the agreement should be explained in the letter.
- End the response letter with a concrete next step or timing request tied to the closing process.
- Avoid unnecessary commentary; the deliverables should read as working documents ready for circulation.