Flows workflow logoFlows
Add a Plan/Todo System to Your Agent
0/4 steps0%

Step 1 of 4

Design the todo data model and tool

Structured plans beat prose plans because the harness can enforce them.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Design a todo subsystem for the agent. Data model: a list of items, each with id, content (imperative phrase), and status (pending | in_progress | completed). Tool interface: todo_write(items) replaces the full list (simplest correct design - the model always sends the complete list). Harness rules to implement: reject lists with more than one in_progress item; reject status regressions from completed to pending without an explanatory note field; store the list in loop state, not in the message history. Write the tool schema and the validation rules first.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A todo tool schema plus harness-side validation rules.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent