dayfinggg

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.

Design types, interfaces, module boundaries, and ownership before implementing a non-trivial feature or structural change. Use when an early design choice would constrain several files or components. Do not use for a small local edit or when an approved…

Prepare and assign one bounded, independently verifiable subtask to a subagent. Use when delegation is available and authorized, one work unit can proceed without shared mutable state, and parallel or specialized work will materially help. Do not use merely…

Reproduce a failure, regression, or performance problem and identify its root cause with evidence. Use when the user asks why something is broken, failing, crashing, flaky, or slow. Do not modify the implementation unless the request also asks for a fix.

Transfer active engineering work to another agent or session without losing decisions, evidence, or the next executable step. Use when the user requests a handoff, work must continue elsewhere, or context limits threaten continuity. Do not use as a generic…

Determine what a proposed or completed change could break outside its immediate diff. Use for blast-radius analysis, shared contracts, migrations, risky refactors, and changes to public interfaces or persistent data. Do not use for a general code review with…

Make an authorized code or configuration change from a settled request, specification, or task. Use when the user asks to build, fix, add, or change something and the implementation scope is clear. Do not use for diagnosis-only, review-only, or planning-only…

Maintain a compact evidence-backed decision trail for long-running, unattended, or high-risk engineering work. Use when later reviewers must understand what changed, why, and what proved it. Do not activate for routine short tasks or duplicate ordinary…

Move code, callers, data, configuration, or dependencies from an old contract to a new one with explicit compatibility and rollback decisions. Use for API, schema, framework, dependency, or storage migrations. Do not use for a simple isolated replacement with…