← ClaudeAtlas

comprehensive-planlisted

Build ONE comprehensive financial plan in a single deliverable by orchestrating the public planfi MCP — retirement/FIRE projection with Monte Carlo backtesting, 529 college funding status, estate-tax exposure, and life/disability protection gaps, every number engine-computed. Use whenever someone asks for "a financial plan", "build me a financial plan", "give me a complete / comprehensive / full plan", "I want one full plan covering retirement, college, estate, and insurance", "do a complete financial review / checkup", or wants one cohesive document instead of several separate analyses — e.g. "build me a financial plan, I'm 40 making $150k with $300k invested" or "give me a comprehensive plan covering everything".
KameronKales/planfi-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill KameronKales/planfi-skills
# Comprehensive Plan A thin orchestration layer over the **planfi MCP** (https://ai.planfi.app/mcp, public, no auth). All math + the 150-year Shiller market dataset live server-side. This skill only gathers inputs and calls the tools — it does **not** compute anything locally, carries no business logic, math, or defaults, and is read-only (it never changes the user's data). The server is the source of truth. This is the **"one document" superset**: it chains four engine sub-analyses — retirement/FIRE, 529 college funding, estate-tax exposure, and insurance/protection — into a single cohesive plan where every dollar is engine-computed. For a **FIRE-only deep dive** (savings/retirement-age/spend trade-offs, goal-solving, scenario comparison), use the **`financial-forecast`** skill instead; come here when the user wants the broad, multi-section plan. ## Step 0 — Make sure the planfi tools are connected This skill uses these tools (may be namespaced, e.g. `mcp__planfi__assemble_comprehensive_plan`): `assemble_comprehensive_plan` (the orchestrator), plus `generate_financial_plan`, `generate_financial_insights`, `generate_action_plan`, `analyze_estate_exposure`, `analyze_529_optimization`, `analyze_insurance_needs`, `run_backtesting` for follow-on deep dives. Use whichever name your environment exposes (bare or `mcp__planfi__`-prefixed); below they are written bare. If they're NOT available, tell the user to connect the MCP, then continue: ``` claude mcp add --transport http