next-tasks

Use the cached engineering Project Tasks and current user priorities. Inspect scoped details for the best ready candidate, including dependencies and recent activity. Explain the selection briefly and begin within existing authorization. Ask only for a material priority or scope conflict. Reuse the Task and binding; do not create duplicate local YAML or issue-tracker records. GitHub/Linear procedures apply only to explicitly assigned issues. Follow `AGENTS.md`. For confirmed bugs, use existing browser observations, logs or failing checks and proceed within the approved scope. Investigate only unresolved uncertainty; do not require a fresh failing baseline. Maintain coverage and verify the fix.