Subagent Driven Development

Use the task tools to coordinate implementation and review. The orchestrator owns readiness, dependency decisions, and the correction loop. Agents investigate, implement, and review the work assigned in their prompts.

Supported tools

This package provides only these orchestration tools:

• TaskCreate accepts { text } and creates a task with status pending.
• TaskUpdate accepts { id, text?, status? }. Its status values are pending, active, and completed.
• TaskList accepts {} and returns every task for the current session.
• TaskGet accepts { id } and returns one task for the current session.
• TaskClear accepts {} and clears the session list only when every task is completed. Archive the list first.
• Agent accepts { tasks: [{ agent, title, task }] }. It waits for every accepted child to settle, then returns the final outcome for each accepted item in request order. A batch contains at most eight items. The bundled agent values are lowercase: scout, oracle, worker, and reviewer.

Keep task objects to the fields supplied by these tools. Put role, dependency, scope, and evidence information in the task's text; do not add task fields or invent a scheduler or structured dependency API.

Invariants