Planning & Project Management for Claude Code

Master orchestrator for the conference-scheduling pipeline. Runs the four-stage state machine (ingest -> cluster -> elicit -> schedule) across a team of specialist agents, talking to them only through schema-shaped artifacts, verifying each stage's confidence at a gate before advancing, holding and integrating outputs rather than passing them through, freezing its own safety logic against an invariants lock, enforcing the elicitor's outlier-probe diversity floor, surfacing conflicts to the human

Stage 3 collaborative preference agent for the conference-scheduling pipeline — the one a person actually talks to. Reads the theme map and representative talks first so it is grounded, then asks a SMALL number of sharp, choice-based questions contrasting real sessions, holds the person's interests as an uncertainty region it narrows with each answer, deliberately probes outliers to fight selection bias, and elicits the user-owned objective weights and hard constraints. Stops as soon as the sche

Stage 4 scheduling worker for the conference-scheduling pipeline. Turns the event records, theme affinities, and preference profile into a feasible day-by-day schedule by solving a constraint-optimization problem — hard constraints (no overlap, travel time, capacity, the attendee's must-attends/blackouts) plus the user-owned weighted objective (interest, breadth, pacing/contiguous-free-time, serendipity). Surfaces unbreakable conflicts as decisions instead of silently picking, and names what the

Quarterly strategic advisor for substacker. Synthesizes the corpus, Curator's section map, Growth Analyst's rolled-up weekly data, and writer's stated goals into a 1500-3000 word review. Surfaces three uncomfortable questions (evidence + reasoning + downside), assesses section portfolio, proposes goal diffs, names one bet for the next quarter, identifies kill list. Rolling 13-week windows, NOT calendar quarters. Use quarterly or on-demand when a specific strategic decision is pending (e.g., "sho

Tracks and advises on the long-horizon portfolio — taxable brokerage, 401k, and HSA invested portion — by aggregating asset allocation across all three, computing drift versus target, optimizing contributions (employer match, annual limits, HSA investment threshold), scanning for tax-loss-harvest candidates with wash-sale awareness, and producing rebalance proposals that prefer tax-advantaged accounts. Runs a quarterly retirement projection. Never executes trades. Use as the investment phase of

Plans a weekly H2H Categories matchup strategy — which of the 10 cats (R/HR/RBI/SB/OBP, K/ERA/WHIP/QS/SV) to push, which to maintain, which to punt. Fires advocate (Balancer) + critic (Puncher) variants per matchup. Drives waiver/streaming/lineup priorities for the week. Use on Monday mornings or when planning a weekly matchup strategy.

Plans Yahoo Fantasy Baseball playoff pushes for weeks 21-23 (ending Sep 6). From July onward, identifies players with most games and best matchups in playoff weeks, suggests trade-deadline (Aug 6) targets, evaluates IL stashes. Fires advocate (Aggressor) + critic (Stabilizer) variants. Use after July 1 for playoff positioning, trade-deadline planning, or late-season roster moves.

Plans weekly pitching moves for a Yahoo Fantasy Baseball H2H Categories league with QS/K/ERA/WHIP/SV scoring (no wins). Identifies two-start SPs, favorable spot starts, and rostered SPs to bench on bad matchups. Fires advocate (Stream) + critic (Hold) variants per candidate. Use for weekly pitching strategy, two-start pitcher targeting, spot-start streaming, or K-chasing plans.

An elite forecasting agent that orchestrates reference class forecasting, Fermi decomposition, Bayesian updating, premortems, and bias checking. Adheres to the "Outside View First" principle and generates granular, calibrated probabilities with comprehensive analysis. Use when user asks for forecast, prediction, or probability estimate.

Times the five single-use chips (Wildcard, 12th Man, Maximum Captain, Clean Sheet Shield, Qualification Booster) across the whole FIFA World Cup Fantasy tournament horizon. Maintains a living deployment plan — which chip is earmarked for which upcoming round, the trigger condition that fires it, and the fallback — and answers the per-round question "fire a chip this round, or hold?". At the verify stage it red-teams the evolution engine's offspring on whether a chip actually belongs on a candida

User-facing orchestrator for FIFA World Cup Fantasy. Runs the evolutionary generation loop — spawns archetype strategist teams in parallel, drives fitness/selection/recombination via wc-evolution-engine, has specialists adversarially verify the offspring, then presents a DECISION BOARD of 2-4 weighted options and STOPS for the expert manager to choose. Advisory not prescriptive: surfaces options with full reasoning and dissent, never auto-commits a squad/XI/captain/transfer/chip. Manages the tou

The tournament-theory pillar of the FIFA World Cup Fantasy backroom. Rates per-team fixture difficulty for the round (and across the horizon), estimates progression probabilities (group qualification + each knockout round) via reference-class base rates updated Bayesianly on form, flags weak-group mismatches (powerhouse vs minnow -> attacker captain candidates + defender clean-sheet locks) and fixture SWINGS to plan transfers around. Emits a `fixture` signal that feeds wc-fitness-eval's progress

Estimates the field for FIFA World Cup Fantasy — public ownership and EFFECTIVE ownership (EO = field_own% × (1 + captaincy_share)), the template set vs the differential list, where the field is OVER-CONCENTRATED (a fade opportunity) and where it is UNDER-REACTING to fixture/rotation news (a get-there-first edge), plus coarse tracking of the visible mini-league rivals for leverage moves relative to specific opponents rather than the global field. Emits an `ownership` signal that feeds wc-fitness

Constraint-and-value specialist for FIFA World Cup Fantasy. In the VERIFY stage, red-teams the evolution engine's recombined offspring for BB6 feasibility (budget, nation cap, valid 2-5-5-3 with >=1 legal XI) and value-per-million, emitting a keep/annotate/kill `verify` verdict. During transfer windows and squad builds, generates concrete transfer plans — evaluating transfer ROI against the free-transfer budget and any points hit, handling elimination-driven forced swaps, and scoping the group->

A single population member in the FIFA World Cup Fantasy evolution engine. Spawned once per archetype (genotype) and run in parallel with its siblings by wc-director. Develops its assigned archetype philosophy into ONE complete, valid candidate — a full 15-man squad, a full matchday plan (XI/captain ladder/bench/subs), or a transfer plan — by weighting the shared scout/EV/fixture/ownership signals according to its genotype, then self-stress-tests it with an internal advocate/critic pass before e

The dedicated LENS fan-in reconciler for the FIFA World Cup Fantasy system, spawned by the Director (main thread). Reads the K verify/judgement artifacts a lens fan-out produced (a specialist run once per lens — advocate/critic/…) and INTEGRATES them into one reconciled verdict plus the residual dissent that does not resolve — it never argmaxes ("pick the best one"). Can also reconcile several specialists' reconciled verdicts into a cross-specialist read for the board. Writes a `synthesis` signa

Claude Code guide — interactive onboarding walkthrough and Q&A on setup, best practices, automation, and effective workflows

Efficient skill management with progressive discovery — 410+ production-ready skills across 33+ domains.

吃一堑长一智 — 6-step interactive reflection for personal setbacks. Diagnoses which layer (L1 notes / L2 in-the-moment trigger / L3 default-reaction practice) is missing and routes to the right modality, instead of letting every reflection become another notebook entry.

Validate implementation plans against DRY, YAGNI, TDD principles and best practices. Identifies gaps, anti-patterns, and improvement opportunities before execution. Prevents over-engineering and ensures test-first approach.

Autonomous Claude + Codex review loop. Plan a feature with adversarial pushback, or audit code, all in one window.

Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code

Engineering lead — orchestrates the team, scopes work, controls depth and budget

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

Internal legal controls review — approval workflows, doc governance

Draft compliance policies required by a framework

Support engineer — ticket workflow design, SLA architecture, knowledge base, escalation paths, and support operations at scale

Product strategist — roadmap planning, prioritization frameworks, competitive analysis, and market positioning

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

Revenue & sales engineer — B2B pipeline, deal strategy, pricing, sales playbooks, and enterprise closing