delegation-assessment
Delegation Assessment
Advise whether recorded remaining implementation work is assignment-ready for another implementation session. Remain read-only: the human engineer decides the assignment and the destination session's capability. Do not dispatch work, create a handoff, or modify the plan or repository.
Establish The Remainder
Assess only at a stable execution checkpoint. The originating execution must first record task states, progress, deviations, blockers, and unplanned necessary work in the plan. When the work inventory is still changing or materially incomplete, report that assessment is premature and identify the missing record.
Use the plan path or plan content supplied by the user. Otherwise locate the plan only when the request and repository identify it unambiguously; ask the user to choose when multiple plans remain plausible. Support Markdown and HTML plans without conversion. Read the complete plan, including locked decisions, external inputs, file inventory, dependencies, task details, verification, progress, and out-of-scope boundaries.
Treat the plan as the durable work record. Consult available execution handoffs, run manifests, review findings, deviations, and focused repository evidence only where they could change the assignment recommendation. Resolve repository-establishable facts through inspection. When sources conflict, resolve the discrepancy from available evidence or identify the exact conflict requiring human confirmation; never silently prefer the newest-looking artifact.
Account exactly once for every incomplete, deferred, or blocked task and every substantiated unplanned-work or remediation item. Completed work may supply dependency or boundary evidence but is not an assessment candidate unless current evidence reopens it.
Assess tasks individually by default. Group tasks only when they share an invariant or implementation boundary and cannot be meaningfully assigned or verified separately. Name the grouped task IDs and the reason for grouping. Dependency, phase membership, proximity, or similar filenames alone do not justify a group.
Complete this stage when the recorded remainder is stable and every candidate is accounted for once, or when the exact scope blocker is identified.