Use when documentation has been created or updated and the user has asked to review - MD files, beads issues, specs, or task lists
Use when implementation work is done (or in progress) and you need to verify it matches the original spec, PRD, beads epic, or task list - checks completeness, acceptance criteria, edge cases, and scope creep
Use when creating a fix or feature branch PR for a Gas Town fork (beads or gastown). Triggers on phrases like "fix PR", "feature branch", "create a PR", "work on issue", "submit upstream". Expects a bead ID or will help select one.
Use when diagnosing workspace or tooling health issues, fixing doctor warnings, or when gt/bd tools feel misconfigured. Triggers on "run doctor", "fix doctor", "doctor triage", "health check", "workspace broken".
Use when delivering a beads epic through polecats and the refinery - sets up integration branch, creates convoy, dispatches waves of leaf tasks, monitors progress, runs quality gates, and validates completeness against the original plan
Use when converting a design document, PRD, or task list into beads issues - ensures lossless conversion with proper epic hierarchy, validated dependencies for maximum parallelization, and three independent subagent review passes before execution
Use when adding a new Git repository as a Gas Town rig with Dolt-native beads. Triggers on "add a rig", "set up a rig", "onboard repo to Gas Town", "new rig".
Use when syncing a beads fork with upstream, updating the bd binary, or cleaning up merged PR branches. Triggers on phrases like "sync upstream", "pull upstream", "update fork", "upgrade beads", "clean up branches".