← ClaudeAtlas

year-startlisted

Run the Year-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only, context only. Invoke at the start of a new year.
latuconsinafr/claude-code-config · ★ 0 · AI & Automation · score 65
Install: claude install-skill latuconsinafr/claude-code-config
# Year-Ahead Scan (global, MCP-only) **Replaces the old project-local `/year-start`** (now archived at `Journals/.claude/skills-legacy/year-start/`). Same reasoning as `week-start/SKILL.md`'s header. `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook. **If anything this session suggests a rule should change**, per CLAUDE.md §20.14: add it to CLAUDE.md §21.3, do not act on it. **Context only, persists nothing to `journal_rollups`** — same as `month-start`/`quarter-start`: the old system never wrote a file here either. **It does, as of 2026-08-25, produce a real yearly technical score and fundamental digest** (`write_technical_score`/`write_fundamental_digest`, timeframe `1Y`) — the top of the cascade: a `1Y` fundamental read feeds down through every finer timeframe that doesn't have its own more specific research yet (`resolveFundamentalTimeframe` in `lib/pairs.ts`), and the `1Y` heatmap column is real, same mechanic as every other timeframe. **As of 2026-08-30, it also writes validated levels** (`write_level`, timeframe `1Y`) for any zone from Step 3.2 that clears §3.3's validation bar. Still no verdict, thesis, or hypothetical — those only originate from `/sod`. ## Step 0 — confirm the MCP server is reachable, then resolve the active set Call `get_account_state` first. If it fails, stop and explain `just run` needs to be running. Then call **`get_active_instruments`** — do not assume a fixed instrument set below. ## Step 1 —