judgment-drilllisted

Runs a daily 25-minute product-judgment training session with five stations — Fermi estimation, stock-or-flow diagnosis, third-order consequences, reverse-the-memo, and a Go problem — all built from real, publicly verifiable cases pulled fresh from the web, graded against sources, with a persistent calibration log. Use this whenever the user asks for their daily drill, training, exercises, practice, "the gym", a Fermi question, a stock-or-flow problem, a case to reason through, a Go problem, or wants to review their calibration or streak. Also use it when the user says something like "give me today's session", "let's train", "quiz me", "I want to practise systems thinking", "run the drill", or invokes /drill in any form. Trigger it even when the user only names one station rather than the whole session.
orchimada/judgment-gym · ★ 0 · AI & Automation · score 62

Install: claude install-skill orchimada/judgment-gym

# Judgment Drill A daily training session for product judgment. Five stations, ~25 minutes, built from real cases with public numbers. The design principle behind every station: **commit to an answer before seeing the ground truth.** Experience accumulates on its own; judgment only accumulates when a prediction gets scored. Never reveal an answer in the same message as the question — that turns training into reading. ## The five stations | # | Station | Trains | Box | |---|---------|--------|-----| | 1 | Fermi estimate | Reasoning to a number from priors | 4 min | | 2 | Stock or flow | Diagnosing the shape of a change | 4 min | | 3 | Third-order effects | Consequence chains at scale | 6 min | | 4 | Reverse the memo | Reconstructing strategic logic | 8 min | | 5 | Go problem | Sente/gote, urgency, whole-board sight | 3 min | Read `references/stations.md` for the full brief, generation recipe and grading rubric for each. Read it every session — do not run stations from memory of this table. ## Session flow **1. Load state.** Read the log (see *Persistence* below). Note: current level, the running score, which cases and Go concepts have already been used, and any weakness flagged in the last review. Never repeat a case, a company, or a Go concept that appears in the log. **2. Source the cases.** Search the web for fresh material. Every case must satisfy the verification bar in `references/sourcing.md`: a real number a real person could check today. Prefer small and obscu