jmgirard

Escalate a hard technical question to a Fable-level review via a self-contained Review Brief (RB), and ingest the resulting Review Report (RR). Use when a question needs stronger review than the session can settle - statistical correctness, high-stakes design - or when the user says "fable review", "review brief", or an RR file needs ingesting.

Implement a planned milestone in a cairn repo on its own branch with tests-first tasks and checkpoint commits. Use when the user wants to start, resume, work on, or continue a milestone (e.g. "work on M07", "resume the milestone", "start implementing").

Plan one or more milestones for a cairn repo - investigate, scope, write acceptance criteria, and register them in the ROADMAP. Use when the user wants to plan a milestone, plan new work or a feature, turn an idea or candidate into a concrete plan, or asks "what would it take to build X".

Prepare a release following the active toolchain profile's release-walk - an r-package profile runs the CRAN walk (version bump, NEWS, checks, cran-comments, human submission checklist); a generic profile does a version bump + changelog + tag. Use when the user wants to release, submit to CRAN, cut a version, or prepare a release. Never self-submits.

Project status snapshot, tracking health audit, and next-action routing for cairn repos. Use when the user asks where the project stands, what to do next, "project status", "health check", when returning after time away, or when reconciliation between tracking files and git is needed.

Verify and ship a finished milestone in a cairn repo - fresh evidence for every acceptance criterion, consistency gate, independent code review, and merge on user approval. Use when the user wants to review, verify, finish, ship, or merge a milestone.

Adopt the cairn system in a repo - scaffold the cairn/ tracking files, CLAUDE.md section, and ignore entries; or migrate an existing precursor tracking system. Use when the user wants to set up, initialize, adopt, repair, or migrate to cairn in a repository.

Fix a user-visible bug in a cairn repo, or adopt an incoming external PR that fixes one, without milestone ceremony - regression test first, gate-lite checks, PR, merge on user approval. Use whenever a bug is reported or described ("users report an error in X", "this crashes when...", "fix this bug"), or an incoming pull request needs taking in ("adopt PR

Record an architectural or statistical decision as an ADR. Use when a non-trivial modeling or API choice is made, or the maintainer says "record this decision".

Close out the current task. Use when the maintainer says "finish the task", "wrap up", or "close this out". Runs checks and only marks done on green.

Scaffold a new ICC estimator with its estimand block, test skeleton, and oracle checklist. Use when adding a new ICC variant (e.g. consistency, one-way, multilevel).

Begin the next task on the board. Use when the maintainer says "start the next task", "begin work", or "let's do the next thing".

Report current project state and the next action. Use when the maintainer asks "where are we", "what's next", or "status".

Verify a statistical estimator against numerical oracles (textbook/analytic, established package, seeded simulation). Use before shipping any ICC estimator or when the maintainer asks to "verify" or "check correctness".

Plan a milestone for the hitop package. Use when the user wants to plan, scope, break down, or add a milestone or feature to project/MILESTONES.md, or asks "what should we work on next".

Review and close out a milestone for the hitop package. Use when the user asks to review, verify, finish, complete, or close a milestone, or after implementation work is done and needs checking.

Audit and update hitop's project tracking docs (CLAUDE.md, project/DESIGN.md, ROADMAP.md, MILESTONES.md, LOG.md) so they match the actual state of the code. Use when docs may be stale, after manual changes made without skills, or when the user asks to update, sync, or refresh project docs.

Implement a planned milestone for the hitop package. Use when the user says to work on, implement, start, continue, or resume a milestone (e.g. "work on M3"), or to implement something already planned in project/MILESTONES.md.

Work the next (or a named) task from MILESTONES.md through the full plan → test-first → implement → validate → review → log loop. Use when the user says "next task", "work on B3", "continue the milestone", or asks to pick up milestone work.

Prepare a CRAN release of the circumplex package — checks, versioning, NEWS, cran-comments, submission steps. Use when the user says to prepare a release, submit to CRAN, or cut a version.

Numerically validate circumplex estimation code against independent references and angular boundary cases. Use after any change to ssm_* statistical functions or src/*.cpp, or when the user asks to verify statistical correctness.

Implements the milestone plan already established in this conversation, following CLAUDE.md's dev workflow and definition of done. Use right after planning a milestone in this same session.

Scaffolds a milestone plan against CLAUDE.md and DESIGN.md, prompting for milestone-specific details before producing the plan.

Read-only conformance audit of a completed milestone against CLAUDE.md acceptance criteria/invariants and the DESIGN.md contracts. Use after finishing a milestone, before starting the next.

Implements the milestone plan already established in this conversation, following CLAUDE.md's dev workflow and definition of done. Use right after planning a milestone in this same session.

Scaffolds a milestone plan against CLAUDE.md and DESIGN.md, prompting for milestone-specific details before producing the plan.

Read-only conformance audit of a completed milestone against CLAUDE.md acceptance criteria/invariants and the DESIGN.md contracts. Use after finishing a milestone, before starting the next.

Milestone-driven development workflow for tidymedia. Use when planning, implementing, or reviewing a milestone, requesting a Fable review brief, ingesting a Fable review, or auditing project-tracking health. Triggers include "plan a milestone", "work on M01", "review the milestone", "fable brief", "project status".