Codex First Million

Codex First Million

Turn a vague wealth goal into a compact, inspectable roadmap. The useful result is the report file, not a long chat response.

Language and deliverable

• Detect whether the user writes in English or Italian and continue entirely in that language.
• If the user explicitly requests English or Italiano, honor that choice instead.
• Preserve the user's currency. Ask for country or tax residence only when local context materially affects the plan.
• Generate one native .md report. Do not generate HTML unless explicitly requested.
• Save the report as outputs/<person-or-goal-slug>-first-million-roadmap.md in the current project, or in a user-specified location.
• In the final chat response, provide one sentence and a clickable absolute path. Do not paste the report into chat.

Read the relevant guidance

• Read references/intake.md before collecting or normalizing the user's numbers.
• Read references/calculation-method.md before choosing scenario assumptions or interpreting projections.
• Read references/report-schema.md before creating the roadmap input and final report.
• Read references/financial-integrity.md before researching current financial rules, naming products, handling sensitive information, or describing risk.

Workflow

1. Define the target

• Clarify whether the target means total net worth or investable assets. Default to net worth only when the user does not care about the distinction, and state that assumption.
• Record the target amount, desired horizon or target age, currency, country, and preferred language.
• Do not imply that reaching the target is guaranteed.

2. Collect a compact financial snapshot

• Reuse facts already supplied in the conversation or workspace.
• Ask questions progressively, with no more than four compact questions in one turn.
• Collect only the values required by references/intake.md: income, essential and lifestyle spending, cash, investments, other assets, debts, available time, useful skills, and risk comfort.
• Accept estimates and ranges. Never require bank credentials, account numbers, tax identifiers, exact addresses, or uploaded statements.
• When a value is unknown, mark it as unknown and explain which projection it limits. Do not invent it.

3. Establish the current position

Calculate and explain:

• total assets and debt;
• current net worth;
• annual free cash flow;
• savings rate;
• emergency runway;
• weighted debt cost;
• the gap between the current projection balance and the target.

Use the deterministic generator for final calculations rather than estimating arithmetic in prose.

4. Design three meaningfully different paths

Create exactly three scenarios:

1. Foundation / Fondamenta — emphasizes resilience, expensive-debt reduction, and a contribution level the user can sustain now.
2. Momentum / Slancio — the recommended base case, combining a credible contribution increase with moderate long-run assumptions.
3. Acceleration / Accelerazione — depends primarily on explicit income or business improvements, not on speculative returns.

For every scenario, specify:

• starting annual contribution;
• annual return assumption;
• annual contribution-growth assumption;
• what must change for the scenario to be credible;
• the main failure condition.

Keep return assumptions sober. Never make the aggressive path merely a higher-return portfolio. If a scenario requires contributions above current free cash flow, connect the difference to named income or spending actions.

5. Add actionable income levers

• Propose three to five levers grounded in the user's existing skills, profession, available hours, capital, and constraints.
• For each lever include: why it fits, the first small test, estimated annual potential as a range, time to first evidence, and confidence.
• Label estimates as hypotheses. Do not present hypothetical revenue as forecast income.
• Prefer experiments that can be validated cheaply before requiring material spending.

6. Research only when it improves accuracy

• Use current web research for jurisdiction-specific tax, pension, account, inflation, interest-rate, or product facts that materially affect the roadmap.
• Prefer primary official sources and record direct links in the report.
• Distinguish sourced facts from planning assumptions and user-provided numbers.
• If current research is unavailable, omit the specific claim or label it as an estimate requiring verification.

7. Build the roadmap file

Create an input JSON following references/report-schema.md, then run:

node <skill-directory>/scripts/build_roadmap.mjs <input.json> <output.md>

The generator validates the inputs, computes the metrics, projects all scenarios, calculates milestone timing, and writes the localized Markdown report.

Before delivery, verify:

• the output language matches the user;
• all currency values use the correct currency;
• the three scenarios expose their assumptions;
• no scenario silently depends on impossible cash flow;
• income ranges are labeled as hypotheses;
• no undefined, NaN, placeholder, or broken source link appears;
• the final report opens directly in Codex.

8. Keep the chat response short

Return only a concise status line and the absolute report link, for example:

Your Codex First Million roadmap is ready: [Open the report](/absolute/path/to/report.md)

or:

La tua roadmap Codex First Million è pronta: [Apri il report](/percorso/assoluto/report.md)

Non-negotiable integrity rules

• Treat every projection as a scenario, never a promise or prediction.
• Do not imitate or claim the authority of famous investors, founders, or financial professionals.
• Do not recommend concentrated bets, leverage, hidden-risk products, or specific securities merely to shorten the timeline.
• Do not give definitive tax, legal, pension, or regulated-product advice without current authoritative evidence and appropriate qualification.
• Make negative cash flow, expensive debt, insufficient emergency reserves, and unrealistic timelines visible rather than hiding them behind optimistic returns.
• Never transmit or publish the user's financial information without explicit authorization.

Default output

1. One bilingual-ready native Markdown roadmap
2. Financial snapshot dashboard
3. Reality check against the requested horizon
4. Three transparent scenario projections
5. Milestones at 100K, 250K, 500K, and the target where applicable
6. Three to five income levers
7. 30-day, 12-month, and years 1–3 action plan
8. Risks, assumptions, and sources