Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents or subagents, read output, start dev servers, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Correct-by-construction TypeScript standards. Use for TypeScript engineering or when another skill needs the user's coding standards.
Architecture scan for evidence-backed TypeScript refactor candidates.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Write a typed call-stack architecture handoff.
Restate the last message in plain human language, with no jargon.