Planning check
Before a planning session: which candidate items would pass the Ready gate and what each still lacks, and how much work each person and agent already carries.
What is checked
- Candidates are stories, tasks, defects and subtasks in Backlog, Idea or Analysis — in the initiative chosen in the context row below the top bar (or the whole solution), under one epic, work package or theme, or exactly the codes you name.
- Stories need the Definition of Ready: a binding requirement they implement and at least one criterion they cover. Defects need triage (a severity). Every item needs a description, no open block, its dependencies done and no open question about it. Under the demand gate its initiative must also answer a demand.
- Load shows, per owner and per agent, the active and Ready items they already carry, so new work goes to someone with room.
Then
Fix what is missing, then move the items to Ready yourself — agents never make work Ready. With an enforced Ready gate an item that fails cannot be moved; with an advisory one it moves with a warning. Your agent prepares the list with check_planning.