managing-tax-controversy

Structures tax controversy management with audit defense, protest, and appeals documentation. Use when managing tax audits, preparing protest letters, or documenting audit defense positions.

11 stars

Best use case

managing-tax-controversy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Structures tax controversy management with audit defense, protest, and appeals documentation. Use when managing tax audits, preparing protest letters, or documenting audit defense positions.

Teams using managing-tax-controversy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/managing-tax-controversy/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/finance/managing-tax-controversy/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/managing-tax-controversy/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How managing-tax-controversy Compares

Feature / Agentmanaging-tax-controversyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Structures tax controversy management with audit defense, protest, and appeals documentation. Use when managing tax audits, preparing protest letters, or documenting audit defense positions.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Managing Tax Controversy

## When To Use

- A client receives an IRS or state audit notice (e.g., CP2000, Letter 950, IDR) and needs a structured defense strategy
- Preparing a formal protest letter to IRS Appeals or state equivalent after an adverse examination result
- Coordinating multi-year or multi-entity audit defense across federal, state, and international jurisdictions
- Tracking statute of limitations, consent-to-extend deadlines, and procedural milestones during an active controversy
- Evaluating settlement posture at any stage — examination, Appeals conference, or pre-litigation

## Inputs To Gather

- **Audit notice or IDR**: Full copy of the notice, information document request, or revenue agent report (RAR) with proposed adjustments
- **Tax returns at issue**: Filed returns for all periods under examination, including amended returns and elections
- **Supporting documentation**: Workpapers, substantiation records, third-party statements, and prior correspondence with the examining agent
- **Entity and jurisdictional details**: Entity type, filing jurisdictions, transfer pricing exposure, treaty positions, and any pending related examinations [VERIFY — confirm all open audit years and jurisdictions]
- **Statute of limitations status**: Dates of original filing, any extensions (Form 872 / 872-A), and current expiration dates
- **Prior controversy history**: Past audit outcomes, closing agreements, or Appeals settlements that may establish precedent or consistency positions
- **Client risk tolerance and objectives**: Settlement authority, appetite for litigation, reputational considerations, and budget constraints

## Workflow

1. **Triage the Notice**
   - Classify the controversy type: correspondence audit, office exam, field exam, TEFRA/BBA partnership proceeding, or international (LMSB/LB&I campaign) [VERIFY — confirm current IRS organizational structure and campaign applicability]
   - Identify the proposed adjustments and compute the tax, interest, and penalty exposure
   - Check statute of limitations — determine whether a consent to extend has been or should be requested
   - Confirm whether the issue is a factual dispute (documentation gap) or a legal/interpretive dispute (authority-based)

2. **Build the Defense File**
   - Organize documents by issue, mapping each proposed adjustment to the taxpayer's position and supporting authority
   - Prepare an issue-by-issue analysis: state the facts, cite the applicable IRC section, regulation, and relevant case law or rulings
   - Identify weaknesses — flag positions where documentation is thin, authority is adverse, or the factual record is ambiguous
   - For international issues, address treaty-based positions, transfer pricing methodology (IRC §482, OECD Guidelines), and any Competent Authority considerations

3. **Draft the Protest or Response**
   - For 30-day letter responses: prepare a formal written protest including the required elements — taxpayer identification, tax periods, itemized adjustments, statement of facts under penalties of perjury, and statement of law [VERIFY — confirm current IRS protest requirements per IRM 8.6.1]
   - For IDR responses: provide responsive documents with a cover letter preserving objections and limiting scope
   - For state controversies: follow the specific protest format and deadline rules of the taxing jurisdiction [VERIFY — state-specific rules vary significantly]

4. **Manage the Appeals Process**
   - Prepare a pre-conference memorandum summarizing the issues, hazards of litigation for both sides, and settlement range
   - Develop a concession strategy — identify issues to concede early to strengthen credibility on high-value positions
   - Track the Appeals officer's settlement authority and escalate to IRS Counsel referral if necessary
   - Document all oral communications with contemporaneous memos

5. **Assess Litigation Readiness**
   - If Appeals is unsuccessful, evaluate forum selection: U.S. Tax Court (pre-payment), U.S. District Court or Court of Federal Claims (refund suit requiring full payment) [VERIFY — confirm jurisdictional requirements and filing deadlines]
   - Prepare a litigation risk assessment with probability-weighted exposure analysis
   - Identify expert witness needs (valuation, transfer pricing, industry practice)

6. **Report and Track**
   - Maintain a controversy status dashboard: issue, stage, exposure, next deadline, and responsible party
   - Provide periodic status reports to the client with updated exposure estimates and strategic recommendations
   - After resolution, document the outcome for use in future compliance positions and audit defense

## Output

- **Controversy Status Report**: Summary of all open issues, current stage, exposure (tax + interest + penalties), statute dates, and next action items
- **Protest Letter or Formal Response**: Issue-by-issue written protest or IDR response ready for filing
- **Appeals Strategy Memo**: Pre-conference memorandum with hazards analysis, concession strategy, and recommended settlement range
- **Exposure Analysis**: Probability-weighted matrix showing best case, likely case, and worst case outcomes per issue
- **Milestone Tracker**: Timeline of all critical deadlines — response due dates, statute expirations, conference dates, and filing windows

## Quality Checks

- Verify all statute of limitations dates are current and no deadlines are at risk of expiring without action
- Confirm each proposed adjustment is addressed individually — no issues are left uncontested without an explicit concession decision
- Cross-check cited authority (IRC sections, regulations, case law) for accuracy and current validity
- Ensure the protest letter meets all procedural requirements for the specific jurisdiction and forum
- Validate exposure calculations including interest computation methodology (IRC §6621 rates, compounding) and applicable penalties (accuracy-related under §6662, fraud under §6663) [VERIFY — confirm current underpayment interest rates]
- Confirm the defense strategy is consistent with positions taken on filed returns and in prior audit cycles
- Flag any positions requiring disclosure under IRC §6694 (preparer penalties) or §6662 (substantial authority / reasonable basis thresholds)

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.