six-month-checkpointlisted

RETIRED 2026-08-23 — do not invoke. Superseded by CLAUDE.md's whole-file rewrite, which removed the six-month/trial framing in favor of ongoing evaluation at every quarterly/yearly rollup (§13/§17). Kept here as inert archive only, same reasoning as the old project-local /checkpoint this itself once replaced.
latuconsinafr/claude-code-config · ★ 0 · Data & Documents · score 65

Install: claude install-skill latuconsinafr/claude-code-config

# Six-Month Checkpoint (RETIRED — inert archive, do not invoke) **Do not run this skill.** `CLAUDE.md`'s 2026-08-23 full rewrite retired the six-month/bounded-trial framing this skill was built around — the practice is now explicitly a lifetime one, and §17 states plainly that "there is no fixed evaluation deadline" and that process compliance is reviewed at every quarterly/yearly rollup instead of one special one-time checkpoint. This file's entire premise (`Day 1 of this practice was 2026-08-04; the six-month mark is approximately 2026-02-04`, Step 1 below) no longer matches what CLAUDE.md says. **The one substantive thing this skill did that survived the retirement** — the equity-based hard stop (§17: `hard_stop_percent_of_cumulative_deposits`) — was never time-bound to begin with and is unaffected; it's still live, still checked via `get_account_state`'s `hardStopThreshold`, just not through this skill. Left in place, unused, for the same reason the old project-local `/checkpoint` and files like `journal/`/`metrics/`/`account/` are — as a record of what this replaced, not something to resurrect. If a comparable one-time milestone review is ever wanted again, it should be designed against the current CLAUDE.md (lifetime framing, live DB values via MCP), not by un-retiring this. --- *Original content preserved below, unmodified, for reference only.* # Six-Month Checkpoint (global, MCP-only) **Replaces the old project-local `/checkpoint`** (now archived at `Journals/.