02
Scope & Pricing
waits for your approvalRead the task notes with task_notes_list: the note from the Requirements step contains the client's needs, deliverables, and constraints. Work from it.
Define scope and pricing. What good looks like:
- A scoped list of deliverables, each with what is and is not included
- Timeline or phases
- Pricing for each deliverable or a clear total, with the model (fixed, retainer, hourly) stated
- Explicit exclusions, so scope creep has a boundary
- Assumptions the price depends on
Save the scope and pricing as a task note with task_notes_add. Then ask the operator to approve the scope and the numbers before any drafting. This is a checkpoint: committing to a price is the judgment moment, so the AI cannot advance until you approve.
no rejection path · the run moves on only when approved