heir-check

estate beneficiaries finance checklist hygiene
by @iberry420finance
Build an education-only beneficiary and estate-hygiene checklist: who is named on accounts, what a beneficiary form vs a will actually does, and a document-location card. Use when the user wants estate basics, beneficiaries, or what happens if I die. No legal drafting or brokerage APIs.
SKILL PACKAGE

Directory layout for Grok — SKILL.md plus scripts, references, and assets. 6 file(s).

Select a file

Edit in place, then Save (full package security scan). Use fullscreen for a larger workspace.

SYNCED SUMMARY (from SKILL.md)
# Heir Check

Titles and named beneficiaries beat a drawer full of intentions. Education only.

Inspired by kusandriadi/finance estate-planning.md (MIT). Original Grok remake. Country-neutral. Not legal, tax, or financial advice. Complements cover-map (insurance) and cash-plan (cash) without replacing them. Do not write a will, trust, or power-of-attorney as if it were a legal instrument.

Read `references/rails.md` before you write. Fill the three templates.

## When to use
- Estate basics, beneficiaries, TOD / POD, who inherits
- Document location card, "what if I die"
- Hygiene checklist: who is named on which *type* of account

## When NOT to use
- Draft a binding will, trust, or power-of-attorney
- Probate representation or local statute invention
- Collect SSNs or account numbers into skill files
- Sell insurance (use cover-map), budget (use cash-plan), invest (use invest-map)
- Brokerage or bank APIs, credential help

## Inputs
- Country context if known (keep products generic; do not invent statutes)
- People who matter: partner, kids, backups (roles, not full legal briefs)
- Account *types* they hold (retirement, life, joint, payable-on-death, taxable, property) — never numbers
- Whether a will / local equivalent already exists (yes / no / unsure)
- Whether dependents exist and life cover is named (gate to cover-map)

## Procedure
1. Read `references/rails.md`. Refuse legal drafting, credential help, and storing account numbers.
2. Country-neutral: talk about "named beneficiary on the account" and "a will your local lawyer would write". No Indonesia-only products (waris, hibah as requirements) and no US-only forms as mandatory. Mention TOD / POD / beneficiary designation as a generic pattern when relevant.
3. Split: (a) things that often pass by beneficiary form / title (retirement, life, joint, payable-on-death) vs (b) things that usually need a will or local equivalent. Say they should confirm locally. Do not invent statutes.
4. Build a name-list: person + role (partner, kid, backup) + which *type* of account (not numbers). Flag missing backups.
5. Document-location card: where the will / insurance / deed / password-hint letter *would* live. No passwords. No account numbers.
6. One next talk: who they need to tell (executor-ish person, partner). Not a scripted legal consult.
7. Cover-map first if they have dependents and no life cover named. Heir-check does not sell policies.
8. Fill `templates/name-list.md`, `templates/doc-card.md`, and `templates/next-talk.md`.

## Output format
- Name-list (people × account types, backups flagged)
- Document-location card (places only; no secrets)
- Next-talk card (who to tell; one educational next step)
- One line: educational hygiene checklist; not legal advice; confirm locally with a licensed attorney / notary

## Safety
- Follow `references/rails.md` with no exceptions.
- No legal instruments drafted as if binding. No SSNs. No account numbers. No brokerage APIs.
- Crisis / self-harm: stop and point to local help; in the US, 988.
- Licensed attorney / notary for real documents.

## Stop conditions
- Checklist + doc card + next talk delivered, or refused for legal drafting / credentials / wrong scope
Version History
Comments (0)
No comments yet. Be the first!
Sign in to leave a comment.