Personal CFO Scenarios

An AI-OS capability with scoped context, local configuration, and reviewable outputs.

Outcome

Dated input data, auditable calculations, a scenario comparison, and sensitivity report. Save deliverables to projects/fin-personal-cfo/{YYYY-MM-DD}_{name}/ with dated filenames. Knowledge skills also maintain their scoped raw/wiki corpus; integration and authoring skills may modify the explicitly selected project.

Context Needs

Dependencies

Skill Relationships

Use the linked skills only if installed; check their SKILL.md and local overrides before invoking. Consume related source artifacts without duplicating their workflow. Keep trigger boundaries stated in the description. Keep durable source pointers with the dated project report. Use meta-memory-write only when the user asks to remember a concise working fact; full research and financial records stay in project files.

Step 1: Load scope and corrections

Check the runtime before reading local context. With Team connected, the authoritative workspace snapshot supplies context and feedback; do not read or write local brand_context, context, or learnings. Use its configured output/feedback mechanisms and report a missing snapshot instead of a local fallback. In Solo mode, resolve the AI-OS root or explicitly active client and read only that scope’s listed brand files, this skill’s learnings, relevant General feedback, and local override. In Solo mode, resolve user configuration as ${AI_OS_SKILL_CONFIG_DIR:-context/config}/fin-personal-cfo/ relative to that workspace; do not reuse another client’s settings. Read relevant assets/ examples if present; use the output template until an approved example exists.

Step 2: Select scenario and gather inputs

Use references/templates/house.md for housing. Other modes—refi, cash flow, big purchase, side income, savings—use the general calculator methods and a task-specific schema, not nonexistent templates. Establish jurisdiction, currency, horizon, income, liabilities, costs, and provenance for each input. Read the detailed method for this step’s mechanics and output shape.

Step 3: Build realistic comparisons

For housing compare baseline, accessory unit, bedroom rentals, combinations, and staged rentals when relevant. Include closing cash, renovations, vacancy, owner-paid utilities, fees, taxes, insurance, and personal comfort. Let the user’s property and lifestyle determine the actual scenario set. Read the detailed method for this step’s mechanics and output shape.

Step 4: Calculate and audit

Read references/calculators.md. Compute debt service, monthly/annual net costs, initial cash, paydown, and alternative-return scenarios. Use consistent units and distinguish nominal versus real returns. Tax effects are jurisdiction-dependent estimates, not automatic US deductions. Test vacancy, rent, rates, maintenance, renovation overruns, and returns. Read the detailed method for this step’s mechanics and output shape.

Step 5: Present sensitivity and decision inputs

Write comparison, assumption ledger, detailed report, and unresolved questions. Show which choice is cheapest, which is resilient, and how lifestyle changes the answer. Highlight thresholds and downside scenarios rather than a single optimistic point estimate; do not treat modeled returns as guaranteed. Read the detailed method for this step’s mechanics and output shape.

Step 6: Save and verify output

Create projects/fin-personal-cfo/{YYYY-MM-DD}_{name}/ in the selected workspace. Date-stamp generated filenames as {YYYY-MM-DD}_{descriptive-name}.{ext}. Keep an index of prior deliverables when revisits are useful. Verify factual/source coverage, schema, calculations, destination fit, and links as appropriate. Store raw inputs only in the authorized local scope; do not mix client data. For publishable prose only, run tool-humanizer if installed; otherwise edit for natural language, concrete claims, the user’s voice, and unsupported promises. Do not rewrite quotations, code, or structured data through this gate. Show a concise preview, report the full absolute deliverable path, and distinguish completed work from unmet dependencies.

Step 7: Capture feedback

Ask for feedback after major deliverables. In Solo mode append dated, contextual feedback under ## fin-personal-cfo in the scoped context/learnings.md. Save an approved good output as an asset only when the user authorizes it; keep private source data out of shared assets.

Rules

• Team snapshot authority takes precedence over all local context/config/knowledge instructions in this entrypoint and its references.
• Read Rules and local overrides before every Solo run. User task authorization and AI-OS project rules govern actions.
• Check actual connector/CLI availability and authentication; use a documented local/manual fallback when absent.
• Never send, post, schedule publication, purchase, or push to a remote merely because a source example shows it.
• Keep base definitions immutable during ordinary use; store corrections in SKILL.local.md.
• No financial transactions or filings; assumptions and uncertainty are part of the deliverable.
• Use current sourced evidence or clearly disclosed assumptions, never fabricated rates or comps.

Self-Update

With Team connected, use only the authoritative snapshot’s configured feedback/update mechanism; do not modify local context or skill rules. In Solo mode, when the user flags a wrong approach, format, assumption, or tone, immediately add the dated correction to ## Rules in adjacent SKILL.local.md, then log it under ## fin-personal-cfo in context/learnings.md. Create the local override if absent. Preserve existing local entries and leave the shipped SKILL.md unchanged.

Troubleshooting

• Missing configuration or source: ask for the necessary input, then continue independent local work.
• Missing optional tool: use the declared fallback and state the coverage limit.
• Missing required native skill: stop only the dependent step and report its exact name.
• Reference command differs from installed tooling: read current official docs; do not pretend the command succeeded.