Resolve material product, behavior, scope, interface, migration, or acceptance decisions that evidence cannot safely determine. Use only while such decisions remain unresolved, not merely because work is large or multi-stage.
Assess, design, or evolve module, data, runtime, deployment, or team-ownership boundaries. Use when those boundaries or responsibility contracts are the task; skip isolated code changes, folder cleanup, and refactors that leave boundaries intact.
Design, implement, or review UI/UX when a user-facing surface needs product, interaction, visual, accessibility, design-system, responsive, or public-web presentation judgment. Skip backend, mechanical frontend work with a settled design, and generic code…
Isolate an unknown cause of a bug, regression, flaky failure, or performance anomaly through reproducible evidence. Use when the cause is uncertain; skip straightforward changes with a known cause.
Resolve unclear business meaning, invariants, consistency ownership, or bounded-context boundaries. Use only while one of those domain decisions remains material; skip technical module reorganization, generic architecture, CRUD, utilities, and styling.
Deliver an approved scoped change and map its acceptance criteria to implementation and observed evidence. Use for criterion-driven implementation; skip review-only, planning-only, and unresolved product decisions.
Apply language- and platform-specific engineering rules to retained source code being created or changed. Use for implementation quality and configured gates; skip review-only work, disposable experiments, and generated or vendored code.
Review a concrete diff, pull request, patch, or completed change for material defects and unmet requirements. Use only when a changed artifact exists and review is requested; skip greenfield assessment and remain read-only unless fixes are requested.