Add a feature to this repository the safe way — spec, locate via maps, respect Stability, surgical implementation, verification, knowledge update. Use whenever the user asks to add, build, or implement functionality.
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULEMAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Perform a deep test of the codebase, validating functional smoke tests, claim verification, drift checks, license headers, and placeholder checks. Trigger whenever the user asks to run deep tests, check code health, or perform strict verification.
Fix a bug in this repository the safe way — reproduce first, failing regression test, root cause via the maps, surgical fix, review, ledger entry. Use whenever the user reports broken, wrong, or crashing behavior.
Review a completed change against its authorizing spec in fresh context — evidence-based checks, severity-ranked findings, and a written verdict for the human's merge decision. Use when a diff needs reviewing before merge, or when add-feature / fix-bug / implement-spec reaches its review gate.
Read-only codebase exploration. Use to locate code, trace dependencies, or summarize modules without polluting the main context window. MUST be used for heavy reading during /cold-start and /create-feature-catalog.
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
Implement a spec from ai/lab/specs/ exactly as written — zero design decisions, stop-and-report on any spec-vs-reality conflict, tests are the definition of done. Built for lighter implementation models.
Diagnostic gate that checks CLAUDE.md and AGENTS.md for completeness, consistency, and stale artifacts — run right after /cold-start and before /add-feature. Read-only; produces a findings report.
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.