Orchestrates the full development workflow: research → plan → implement, with human review checkpoints between each phase. Use this skill when starting to implement a new feature end-to-end.
Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, 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).
Monitor a PR's CI, re-arm on each iteration, ignore known-flaky errors, stop when green
Reads annotations left by the user and updates the entire document based on their content.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
This is a task to create an implementation plan. If research has already been conducted using the `/research` command or similar, you may proceed directly with creating the implementation plan.