Use when writing, reviewing, or refining Gherkin, BDD scenarios, acceptance criteria, feature files, behavior specs, examples, user journeys, business rules, edge cases, or Given/When/Then wording.
Use when writing, reviewing, editing, or renaming tests, variables, functions, classes, types, components, scenarios, tickets, branches, or other identifiers where names may be vague, implementation-focused, misleading, or hard to understand.
Use when reviewing the active or named branch against a target branch, drafting GitHub review comments, verifying findings locally, or coordinating focused reviewer subagents.
Use for software development feature or bugfix work that should follow a strict red, green, refactor loop with isolated subagents, verified failing tests, minimal implementation, review gates, commits, pull requests, and ticket observations.
Use when validating that an Epic, Feature, parent ticket, or ticket subtree is coherent, dependency-safe, testable, and ready before implementation or TDD orchestration.
Use when building, grooming, or refining an Epic, Feature, parent ticket, or ticket tree before implementation so work can be manually reviewed, promoted from triage, and later executed with TDD.
Use when Codex needs to run an intense evidence-first pull request review against dev, develop, or a named target branch; gather requirements from GitHub PR text, Linear issues, branch names, tickets, and code; use vette risk lanes to find defects; create and verify temporary TDD-style failing tests for high-confidence failures; and draft PR review comments that include the generated test code.
Use when a parent ticket already has child tickets and a Codex/cmux orchestrator must sequence implementation PRs across ticket systems, branches, blockers, and worker tabs.