schedule-worktrack-skill

Worktrack scheduling decides the correct next minimal, bounded set of actions so the harness can refresh its task queue safely without jumping straight into downstream execution.

Dispatch handoff packaging produces a bounded context that includes required references to the worktrack contract, gate criteria, baseline policy, shared facts, and context budget for safe execution.

You need to replan a worktrack task queue when the worktrack is in the scheduling phase and the queue must be replanned after contract state, evidence, or blocking changes occur.

Yes, worktrack scheduling outputs a structured scheduling result that explicitly returns coverage-gap or no-safe-next-action reasons when it cannot find a safe dispatchable action.

Yes, you must consume a WorktrackStateEstimate and required worktrack-scope artifacts to build a dispatch package with gate criteria and baseline policy sourced only from the Worktrack Contract.

Bounded worktrack refresh scheduling limits execution to a single next dispatchable action, preventing overly broad plans and explicitly rejecting execution if no safe next action is found.