Agents In Use
What’s new todayLast update
47 use cases added today

Claude Code turns brokerage exports into a phased portfolio plan

Matt Stockton used Claude Code across multiple sessions to clean brokerage exports, ask clarifying questions and assemble a household portfolio review and phased plan.

OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Review the attached account exports and household constraints. First identify missing or duplicated data and ask me questions before analysis. Show your calculations, flag assumptions, compare options and produce a phased plan for my review; do not make transactions.

Evidence at a glance

Sourced account
Source poster / publisher
Matt Stockton
Original account
Read the source ↗
Published
Source link checked
Reported result
Stockton reports producing and using a detailed phased portfolio plan from multiple account exports; he said implementation was nearly complete, but reported no trades or returns.
Human involvement
Stockton supplied constraints, answered follow-up questions and reviewed revisions. The article does not report completed trades or independent financial review; its personal analysis is not a recommendation for other investors.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. Export account holdings and related fee or cost-basis data to CSV, then place them in a working folder.
  2. Write a separate note for household values or account settings that are not included in the exports.
  3. State goals, preferences, known constraints and suspected problems, and ask the agent to clarify uncertainties before drawing conclusions.

Matt Stockton used Claude Code to work through brokerage CSV exports alongside a plain-text note about details that were missing from the files, such as bank balances, education savings and employer retirement accounts. He also prepared a prompt describing household goals, preferences and accounts he did not want changed.

Across multiple sessions, Claude Code wrote and ran scripts to parse inconsistent files, classify holdings, handle encoding problems and remove duplicated positions from overlapping exports. Stockton then worked through clarifying questions and revised the analysis. He says the agent caught issues in its own draft, including an overweight account and an allocation that would have added to a category that was already too large. The eventual document included a holdings snapshot, gap analysis, fund comparisons, tax considerations and actions grouped into phases.

Stockton says he is using the plan and was close to finishing its implementation when he wrote. He does not report completed trades or verified financial gains. This is a personal analysis workflow, not evidence that the recommendations are suitable for another investor. The strongest reusable part is the preparation: combine exportable data with a clearly marked constraints file, ask for exhaustive questions, and inspect every assumption before acting. The source does not establish independent financial review of the plan.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Blog · Matt Stockton

Frequently asked questions

What did Stockton provide to Claude Code?

He supplied brokerage CSV exports, a text file with additional household financial details, and a prompt describing goals, preferences and account constraints.

How did Claude Code handle messy exports?

Stockton says it wrote scripts to parse files, handle encoding differences, classify holdings and remove duplicated positions from overlapping exports.

Did the plan produce a reported investment return?

No. Stockton says he was using the plan and nearing implementation, but the article does not report completed trades or returns.

More details

Remaining steps

  1. Review its parsing scripts and calculations, correct assumptions over multiple sessions, and treat the resulting plan as a draft for human review.

About this account

Claude Code read local files, wrote and ran parsing scripts, iterated on the analysis and assembled a phased portfolio plan.

Firsthand article opened directly on 2026-10-18. The page identifies Matt Stockton and publication date 2026-02-10. Summary describes his own reported process; no independent verification of analysis or investment outcome is claimed. Suggested prompt written by Agents In Use.

Credit: Matt Stockton

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude Code · Python · Brokerage CSV exports

Portfolio analysis · Brokerage data · Personal finance

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.