Two-stage panel review of a task file BEFORE implementation. Stage 1 (framing & scope — archaeology/altitude, YAGNI + intermediate-goal scoping, product vision) is resolved and the file edited FIRST; Stage 2 (conformance — architecture/mesh, security, test-strategy) then reviews the cleaned file. Each stage adversarially verifies findings before you see them. Use when a task file is ready for design review, when the user says "review the X task", or before saying "go" on implementation.
The "go" procedure — implement a reviewed task file phase-by-phase, then fan out adversarial verifiers that check each phase against its own success criteria + .claude/rules/ (which /code-review can't do because it doesn't know the task file). Use when the user says "go"/"implement"/"build" on a task file that has already been through /review-task (or equivalent design review).
Convert audited @skip-check code blocks into @check-example annotations or flag @skip-check-approved candidates for human approval. Use after /doc-example-audit, before publishing docs.
Manually-invoked bedtime self-improvement pass (v0, thin). Picks ONE easy-to-review candidate from tasks/nightly/backlog.md, does a small findings-only review, and writes a triage-optimized morning digest to tasks/nightly/<date>.md. Invoke EXPLICITLY at bedtime via /nightly-pass — never auto-trigger.
Audit @skip-check annotations in website docs (.md/.mdx) — categorize each block and produce a prioritized conversion plan. Use before starting Phase 2 doc work.
Publish all packages to npm with synchronized versioning (Lerna). Use when the user wants to release, publish, or cut a new version of the packages.
Verify @skip-check-approved code examples against actual source code — catch stale or incorrect examples before release. Use as a pre-release check.
Workflow selection for new tasks — docs-first vs task-file-first. Use when starting a new task or creating a task file.