Safety gate for work on production, shared infrastructure, live harness paths such as /.agents, /.claude, or /.codex, or unfamiliar code where the next action could damage shared state. Invoke it before a destructive command; it pauses only the high-risk action for confirmation while reversible work continues.
Root-cause route for an observed error, crash, regression, failing test, or intermittent behavior whose cause is still unknown. Reproduce it, name the evidence-backed cause before editing, verify the fix with a red-capable check, and scan for siblings. Use review for diff review and ui for taste complaints.
Explicitly requested, read-only survey for a repository area where the best architecture investment is unknown; ranks evidence-backed seams in a visual report for the user to choose before a later Grilling Session.
Decision probe for one unresolved logic, state, or visual design question that is cheaper to experience than discuss. Build a throwaway terminal driver or UI variants, capture the verdict in the brief, then stop. ui implements a chosen visual direction; production work remains a separate human-selected task.
Browser evidence route when UI changed, browser acceptance remains unproven, or the user asks to test a page. Requires host browser automation; maps the current artifact to acceptance criteria and stores a PR-ready handoff for ship. Use review for the diff and native tests for non-UI behavior.
Review a code diff when asked, before committing, or before a PR. Uses scoped evidence, risk lanes, bounded correction, and cold-context escalation. NOT browser QA, prepared-plan critique, or external artifact trust checks.
Delivery route after coding work is complete and the user asks to ship, create a PR, or publish the branch. Run test, scope, and review gates; commit relevant files; push a non-default branch; then upsert the PR and available QA evidence. Unfinished work returns to its execution owner.
Pre-adoption trust route when an external skill, MCP server, repository, URL, package, API, SDK, or service may be installed, executed, granted access, or trusted. Classify STRIDE, follow the artifact-specific review, and return adopt, restrict, or reject. High-risk paths require human approval; rejected paths stop…
Cross-session navigation route when one destination depends on several decisions whose dependencies or evidence cannot fit the current Grilling Session. Create a named map or resolve one human-selected unblocked entry, optionally through prototype; update the frontier and stop before implementation.
Production UI craft route when a page or component needs a committed visual direction, or a taste complaint such as 不好看、突兀、死板、沒回饋感 needs correction. Name the direction, implement required states, and verify rendered locales. Use prototype while direction is open, debug for render failures, and qa for browser…