← Back to library

Prepare your side of a tax dispute with three Claude tools

Thetangstr, a homeowner contesting a disputed solar credit before Tax Court without an attorney, split the work across Claude tools: the browser extension read each filing in the court portal, the desktop app tested records against the credit's rules and drafted a settlement proposal, and Claude Code merged fifteen PDFs into one exhibit packet.

  • OutcomeUnderstand an IRS case from the court portal, check your records against the credit's rules, and send the agency's lawyer a settlement letter backed by one merged evidence file.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditThetangstr
View original
Works with
ClaudeClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You represent yourself in a tax or benefits dispute and the case file lives in an online portal
  • Your proof is spread across downloads, email and photos
  • You need a calm, organized letter rather than a court filing

Not for: Anything where you are unsure of deadlines or rights; ask a tax professional or clinic first; Filing documents with the court on your behalf

What do you need, and what do you get?

You need

  • Login to the court or agency portal
  • Contracts, permits, receipts, certifications and photos that support your claim
  • The published requirements for the credit or deduction in question

You get

  • A dated timeline of the case and a plain-English reading of the agency's position
  • An evidence checklist mapping each document to a requirement
  • A settlement letter draft you edit and send yourself
  • One merged PDF of exhibits

How does it work, step by step?

  1. Let the browser agent read the docketOpen the portal yourself, then ask the extension to open each filing and return a timeline, the agency's argument, the deadlines and how strong the argument looks.
  2. Move the summary to a workspace with your filesPaste that summary into the desktop app alongside your own documents and the rule text for the credit.
  3. Test your proof against each requirementAsk for a table that pairs every legal requirement with the document that satisfies it and flags any gap.
  4. Draft the letter, not a filingHave it write a short settlement proposal to the opposing attorney that summarizes the evidence; you edit tone and facts before sending.
  5. Bundle the exhibitsUse a coding agent to merge the supporting PDFs into a single ordered file you can reference in the letter.

The prompt

Our own prompt, inspired by Thetangstr and written to work in Claude and Claude Code. Values in lime are placeholders.

Prompt0 variables
I am representing myself in a [tax / benefits] dispute. 1) From the portal pages I open for you, list every filing with its date and summarize what the other side claims and on what basis. List all deadlines. 2) Using the requirement text I paste, build a table: requirement | my document that proves it | gap or weakness. 3) Draft a polite settlement letter to [opposing counsel] proposing resolution without trial, citing only documents in the table. Do not state legal conclusions as certain and mark anything I must verify.

Inspired by Thetangstr: How I Used AI to Fight the IRS (And Why I’m Probably Going to Win). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • The case was still pending when the author wrote it up, so treat the result as unproven; the workflow is the takeaway.
  • He traced the mess to notices going to an old address and incomplete replies; update your mailing address with the agency as soon as you move.

Our take

The useful idea is matching each tool to where the information lives: a portal only a browser agent can reach, local files for the desktop app, and a mechanical merge for the coding agent. That pattern travels well to benefits appeals, insurance disputes and any self-represented paperwork fight. Be strict about the boundary the author kept: the assistant reads, organizes and drafts, while you check every claim against the actual rule text and decide what to send. For anything involving court deadlines, a free low-income taxpayer clinic or a tax professional is still worth a call. Never miss a filing date because you were waiting on an agent. Keep exhibits numbered and unchanged once filed. Store credentials to court portals carefully. Treat settlement letters as drafts until counsel or you personally approve. Verify every cited regulation against the official text, not a model paraphrase. Calendar every deadline in your own system the day you learn it.

Where the time goes back: Reading a dozen dense filings and cross-checking them against scattered personal records is the slow part; splitting that across a browser agent, a desktop chat and a file tool removes most of it.

FAQ

How long did it take?
He estimated six to eight hours by hand; the assisted version took about thirty minutes, and merging the PDFs took seconds.
Did the AI file anything with the court?
No. It summarized, checked and drafted; he sent the letter himself and kept the decisions.

Source and credit

Inspired by Thetangstr. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How I Used AI to Fight the IRS (And Why I’m Probably Going to Win)
Creator
Thetangstr
Published on
Medium
Original date
Jan 8, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; nothing was sent, filed, purchased or published.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Money & Admin

All 82 Money & Admin playbooks →

Related playbooks

Money & AdminWorkflow✓ AI dry run

Match apartment defects to the housing code before filing

A documented list of your apartment's problems, each tied to the code section it breaks and the building's public violation history, ready for complaints you file yourself.

Credit: Argona0x (@Argona0x)

An afternoon+
Money & AdminWorkflow✓ AI dry run

Research a purchase down to delivered price and codes

Have agents compare a product across shops with real shipping, tested coupon codes, price history and owner reviews before you buy.

Credit: u/zawaer on r/SideProject

An afternoon+