Individual skill

reflect-3_attempt_03

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_008/reflect-3/reflect-3_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Reflect-3 Advisory Planning SOP

Use this skill for structured private-wealth advisory tasks that ask for Roth/RMD projections, ILIT Crummey funding, GRAT/CRAT comparisons, or combined estate-liquidity action plans.

## Workflow

1. Read the staged prompt, request memo, and answer template first. The template is the contract: return exactly one JSON object, use the enum strings verbatim, and emit numbers as JSON numbers rounded to cents.
2. Query only the task-provided advisory API records needed for the requested output: client profile, source documents, retirement accounts, life insurance, trust candidates, tax policy, and RMD factors.
3. Resolve conflicts before calculating. Do not average conflicting facts.
4. Build the JSON from the template fields, not from prose labels. Sort any `action_set` alphabetically.

## Source Resolution

- Use `SIGNED_PROFILE` for current household facts: age, planning year, filing status, marital status, non-IRA income, marginal rate, beneficiary count, estate value, liquid assets, and repeated profile goals when it is the latest signed source.
- Use `CUSTODIAN_EXPORT` for retirement account balances, expected return, Roth/traditional split, RMD start age, and recommended conversion years.
Back to top