backend-tasks

Break the approved backend scope into the smallest ordered set of verifiable tasks that implement the contract. Small tasks keep the implement→verify→fix loop tight and every change reviewable. Read-only — produces a task list, not code. This is the fallback author: the design phase normally emits tasks.json via /backend-design. Run this only when .maestro/<slug>/backend/tasks.json is absent (e.g. a standalone /backend-impl run with no design phase).

Inputs

feature, contract_summary (the contract the backend OWNS), optional lld_path.