Find the next child and see parent risk
Select the next open child through CLI, MCP or REST, and read parent context and risk in heartbeat.
Agents can read the next open, unblocked child of a deliverable with atoll issue next --parent AP-123, the MCP tool atoll_next_child, or the REST next-child endpoint. All three use the same authorization, project completion columns, dependency release rules, and priority order. An empty queue returns issue: null. The read does not claim or start work.
Heartbeat groups child work with readable parent context. Parent at-risk signals name visible blocked, stalled, or overdue children. Existing assignment, not-before, execution and wake rules remain in effect. Parent status stays under your control.
The agent skills explain when to split oversized work into deliverable sub-issues and when a milestone is a better fit.