handoff-session-loop

Handoff Session Loop

Use this skill only after an explicit user request. It is a Codex-native orchestrator: do not invoke Claude Code commands, Claude workflows, or files from plugin-task-loop/.

Read references/manager.md before selecting work. Before each delegation, read the matching role template in references/ and replace every <placeholder> with the task-specific facts. The templates define the required inputs and report format; the Manager remains accountable for all Handoff state changes.

Prerequisites and safety

1. Confirm that the Handoff MCP tools are available. If they are not, explain that the project must first configure Handoff MCP; do not emulate its task state by editing .handoff/ files.
2. In non-interactive codex exec, confirm that Handoff write calls are explicitly permitted before selecting work. Set mcp_servers.handoff.default_tools_approval_mode = "auto" for the controlled invocation, or use the interactive CLI. If Handoff write calls are cancelled, do not delegate work or leave tasks in_progress; report the configuration blocker instead.
3. Work only in the current project. Never push, publish, deploy, run a migration, or perform a destructive operation without the user's explicit approval.
4. The root agent is the Manager. It retains responsibility for task state and final verification; child agents must not mark a task done merely because their local work appears complete.
5. Treat every child-agent failure, timeout, or missing report as a failed gate, never as a pass.

Start and select work

1. Call handoff_load_context for the current project. If it asks for an active session, immediately call handoff_save_context with session_status: "active", inherited context, a concrete next action, and a checklist item.
2. Call handoff_list_tasks. Select only tasks that are todo, have no unfinished dependencies, and have a clear, independently writable file scope. Inspect each candidate with handoff_get_task before choosing it.
3. If scope, acceptance criteria, required tooling, or file ownership is unclear, leave the task todo or set it to review and ask the user for direction. Do not invent requirements.
4. Form small batches. Concurrent developer work is permitted only when the selected tasks do not share files or generated outputs. Keep one available collaboration slot for the Manager; otherwise run work sequentially.
5. Before delegating a leaf task, update it to in_progress with handoff_update_task. Supply a positive schedule.estimate_hours when required by Handoff.