Implements a scoped unit of work from an approved design doc or plan using caller-first scaffolding, contract freeze, test-first design, then one-function-at-a-time completion. Use when implementing from a spec, scaffolding after a design, or executing a plan slice—not when still planning or comparing options.
Parses the repo and conversation to produce a self-contained markdown advisory brief for an external AI (no codebase access) to evaluate options, recommend a path, and return structured deliverables. Use when comparing architecture, vendors, stacks, or tradeoffs before implementation — e.g. "evaluate DB options", "compare auth providers", "should we use X or Y".
Creates implementation plans following PLANNING_RULES. Use when the user asks to create a plan, write an implementation plan, or plan out work. Ensures Overview, Happy Flow, Manual Verification, Update Runbooks (audit docs/runbooks/), parallel delegation, asset storage, and UI screenshots. Loads phase-specific reference files before each gate.
Produces a concise end-of-session handoff in `handoff.md` summarizing what was done, what remains (with the last to-do you were working on), the PR link, and the key plan/notes files to read next. Use at the end of a work session or before switching agents.
Investigates failing GitHub PR CI checks, reproduces failures locally, fixes scoped issues, commits and pushes, and summarizes changes. Use when CI is red, GitHub Actions or checks fail on a PR, or the user asks to fix CI/build/ lint/test failures for a branch or pull request.
Diagnoses a microservice or pipeline service and produces a refactoring plan focused on modularity, test coverage, lint/type health, runbooks, and service READMEs. Use when the user asks to refactor a service, pipeline, microservice, worker, batch job, or study service and wants a plan before implementation. Slash-only.
Converts user-provided text or image content into LaTeX-only output using inline $...$ and display $$...$$ delimiters with no bracket delimiters and no additional commentary. Use when the user asks to write content in LaTeX with strict output-only formatting.
Reviews plans, proposals, and code changes for unnecessary complexity, unverified assumptions, and premature abstraction. Use when the user asks to simplify a plan, challenge a proposal, narrow scope before implementation, pressure-test whether a design is overengineered, or review a diff for avoidable complexity. Slash-only.