jrittelmeyer

checkpoint

Commit and push pending work, then either continue to the next backlog step (context still healthy) or emit a paste-ready resume prompt plus a recommended relaunch model + reasoning effort for a fresh session (context tight). Use when the user says "checkpoint", "commit and continue", "wrap this step up", or asks whether to keep going vs. clear context.

dep-check

Registry-verify a dependency before adding or upgrading it — check the real published version, tags, and release age; enforce a release-age window; exact-pin frequent publishers; sanity-check peers and maintenance. Use when adding or bumping a dependency, picking a version, or triaging a Renovate/Dependabot PR. Never pick versions from blog posts or model memory.

Data & Documents Listed

doc-audit

Audit and optimize a project's documentation, agent-context files, persistent memory, and showcase docs for accuracy and token efficiency — code↔doc drift, duplication, archiving, memory slimming, showcase currency, standing-instruction budgets. Use when asked to review/clean up docs, context, or memory — or as a periodic maintenance pass to keep them lean and accurate.

live-verify

Verify a change by running it, not by assuming — full gate, fresh production-shaped build, then drive the affected flow end-to-end and observe real output. Use before committing nontrivial product changes, after wiring any integration, or whenever the question is "does it actually work?"

project-adopt

Adopt an existing codebase onto a template/boilerplate foundation — survey it into a parity contract and an honest theirs-vs-foundation disposition map, converge a product brief + migration map, and regenerate the living docs into a port program. Use to adopt/port/migrate an app onto a template or boilerplate, merge/upgrade it with a template's features, or when source code lands in the intake dir.

project-audit

Deep audit of the whole repo — verify docs ↔ code alignment, score each feature group out of 100 against a best-available bar, and emit an exhaustive prioritized backlog that would bring every group to 100. Use when the user asks for a project audit, quality scores, "how good is this really", or "what's missing to make this perfect".

Data & Documents Listed

project-init

Initialize a new product — ingest plan docs or a raw idea, run discovery and competitive research, converge on a product brief, and regenerate the living docs into a build program targeting a 100 audit score. Use on a fresh scaffold from a template, when the user says "init this project" / "here's my idea for an app", or when they hand over plan documents.

retro

Harvest a finished milestone or painful session into durable harness improvements — corrections, surprises, and re-derived knowledge become candidate skill edits, hooks, adapter fields, or memory/instruction lines, each behind the normal sign-off gate. Use after a milestone, after repeated failed attempts, or on "retro" / "make sure this doesn't happen again".

Data & Documents Listed

tidy

Local dev-machine hygiene — prune the project's unbounded build/engine cache to its size cap, report disk + cache size, then surface (not auto-run) the judgment-required cleanups (orphaned dev processes, stale test data, dangling container images). Use at a checkpoint boundary, when disk is low, or when the build cache "is huge" / "clean up the machine".