Quick Start Tutorial

This walkthrough is designed to be runnable in a fresh environment after installation. It uses a small local text file so you can verify the FundAdmin AI workflow without needing a real fund document.

Step 0: Create a sample file

From your shell, create a tiny LPA-like input file:

cat > sample-lpa.txt <<'EOF2'
Limited Partnership Agreement
Fund: Example Growth Fund I, L.P.
Management Fee: 2% of committed capital during the investment period.
Carried Interest: 20% after return of capital and an 8% preferred return.
Reporting: Quarterly reports within 45 days and audited financials within 90 days.
Key Person: If two of the three named executives cease active involvement, the investment period pauses.
Transfers: Limited partners may not transfer interests without GP consent.
EOF2

Then open Claude Code in that same directory:

claude

Step 1: Confirm the command surface

Inside Claude Code, run:

/fund help

You should see the FundAdmin AI command groups, including document review, document generation, compliance, analysis, and reporting workflows.

If Claude Code says the command is unknown, stop here and go back to the Getting Started page.

Step 2: Run the flagship review

/fund review-lpa ./sample-lpa.txt

What to look for:

• a structured review written to your current working directory
• an LPA Safety Score with a grade
• prioritized findings and recommendations instead of a generic freeform summary

Typical sections in the review include:

• executive summary
• score and grade
• key risks
• provision-level findings
• recommended next steps

Step 3: Benchmark the same document

/fund benchmark ./sample-lpa.txt

This step checks that you can move from review into comparison and negotiation-oriented analysis without changing tools.

You should expect output that discusses terms such as:

• management fee structure
• carried interest
• reporting cadence
• key-person or governance terms

Step 4: Translate the document into plain English

/fund plain-english ./sample-lpa.txt

Use this when you want a faster summary for stakeholders who do not want a clause-by-clause legal readout.

Good output here should make the tradeoffs obvious in plain language rather than just repeating fund jargon.

Step 5: Turn the work into a report

/fund report-pdf

This command is the reporting handoff. It uses the latest structured analysis as input for a presentation-ready deliverable.

Before you run it, make sure:

• Python 3.8+ is available
• reportlab is installed

If PDF generation is not configured yet, do that from your shell and then retry:

pip3 install reportlab

Step 6: Try a realistic next action

Once the core workflow is working, pick one follow-up command based on what you would actually do next:

/fund lpa-negotiate ./sample-lpa.txt
/fund check-compliance ./sample-lpa.txt
/fund draft-capital-call <data>

A useful mental model:

• review to identify issues
• benchmark / plain-english / negotiate to decide what to do
• report-pdf to package the result

Step 7: Set up the Inbox workflow (optional)

The Document Intake pipeline automates the drop-classify-track cycle for incoming fund documents.

Initialize the Obsidian vault:

/fund vault-init

Drop a PDF and ingest it:

/fund ingest ./incoming-capital-call.pdf

This classifies the document, extracts metadata, creates a review stub in the vault, and adds it to the Kanban board in the new column.

Ingest from email:

/fund ingest-email

Processes fund documents from your configured email inbox and routes them through the same pipeline.

Sync review outputs to the vault:

/fund vault-sync

Pushes all completed reviews from your working directory into ~/FundAdmin-AI-Vault/ with YAML frontmatter, tags, and backlinks.

The full inbox workflow:

Drop PDF → /fund ingest → vault stub created → Kanban: new
                       ↓
              /fund review-lpa (or other review)
                       ↓
              /fund vault-sync → Kanban: completed

Copy/paste command set

If you want the whole walkthrough in one place:

cat > sample-lpa.txt <<'EOF2'
Limited Partnership Agreement
Fund: Example Growth Fund I, L.P.
Management Fee: 2% of committed capital during the investment period.
Carried Interest: 20% after return of capital and an 8% preferred return.
Reporting: Quarterly reports within 45 days and audited financials within 90 days.
Key Person: If two of the three named executives cease active involvement, the investment period pauses.
Transfers: Limited partners may not transfer interests without GP consent.
EOF2
claude

/fund help
/fund review-lpa ./sample-lpa.txt
/fund benchmark ./sample-lpa.txt
/fund plain-english ./sample-lpa.txt
/fund report-pdf

Common first-run mistakes

Running the slash command before opening Claude Code

Run claude first, then issue /fund ... commands at the Claude Code prompt.

Testing with a missing file

If your file cannot be found, either start Claude Code in the right directory or pass an absolute path.

Expecting a polished PDF without the Python dependency

The markdown workflows can succeed before PDF rendering is ready. Install reportlab when you are ready to use /fund report-pdf.

Treating the sample file as a production-quality analysis target

The small text file is only a smoke test. For meaningful review output, use a real LPA, side letter, subscription package, or other fund document.

What to read next

• Key Concepts — understand skills, agents, outputs, and workflow categories
• Command Reference — browse the full command catalog
• PDF Reports — see how report export is positioned in the product