Menu
Report current project state and the next action. Use when the maintainer asks "where are we", "what's next", or "status".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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".
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".
| name | status |
| description | Report current project state and the next action. Use when the maintainer asks "where are we", "what's next", or "status". |
| allowed-tools | Read, Grep, Glob, Bash(git log:*), Bash(git status:*) |
@project/STATUS.md
Read project/STATUS.md and project/MILESTONES.md (the plan and the task board
live in MILESTONES — ADR-015; there is no TASKS.md). Summarize, concisely:
Do not modify any files (read-only). Cross-check against git: if
project/STATUS.md looks stale relative to recent commits (e.g. it names a task
already completed in git log), say so explicitly rather than trusting it.
Also flag stale transient markers: grep project/ for pending push,
done (local), or in progress, and check each against reality. Use
git status -sb (shows ahead/behind vs origin) and git log — if a
"pending push" milestone/task is in fact already on origin (local not ahead),
or an "in progress" milestone has a fully-checked board, report the contradiction
and name the file/line so it can be reconciled.
Also audit project/REFERENCES.md for lapsed oracle statuses (this file has no
CI gate, so it drifts silently — it once sat two milestones behind). Grep it for
planned / not yet asserted / to be committed; for each hit, cross-check the
milestone it names against MILESTONES.md (is that milestone done?) and the test
file it names (does it exist with expect_ assertions?). If a planned oracle's
milestone has shipped, report it as a lapse with file/line — it should read
asserted.
