← ClaudeAtlas

quarter-startlisted

Run the Quarter-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 quarter.
latuconsinafr/claude-code-config · ★ 0 · AI & Automation · score 65
Install: claude install-skill latuconsinafr/claude-code-config
# Quarter-Ahead Scan (global, MCP-only) **Replaces the old project-local `/quarter-start`** (now archived at `Journals/.claude/skills-legacy/quarter-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 — **this skill cannot adopt rule changes itself.** That's `quarter-end`'s job alone, and only for items already sitting in §21.3 with evidence attached. **Context only, persists nothing to `journal_rollups`** — same as `month-start`: checked the old system first, it never wrote a file here either. **It does, as of 2026-08-25, produce a real quarterly fundamental digest** (`write_fundamental_digest`, timeframe `1Q`) — quarterly is fundamental-only: there's no distinct "quarterly candle" chart resolution, so this session re-reads the *monthly* chart and refreshes `month-start`'s `1M` technical score in place (an upsert, not a new heatmap column) rather than producing a score of its own. **As of 2026-08-30, the same re-read also writes/refreshes validated levels** (`write_level`, timeframe `1M`) for any zone from Step 3.2 that clears §3.3's validation bar — same upsert-in-place framing as the technical score: a quarterly pass can confirm, extend, or invalidate a level `month-start` already logged. Still no verdict, thesis, or hypothetical — those only o