A multi-step AI workflow passes a checked artifact from one request to the next. Each stage has a purpose and a stopping rule. Writing “first extract, then draft” inside one prompt is a multi-part request; separate calls let you approve the handoff.
Example: notes to an approved follow-up
Source notes: “Maya will draft the proposal. Leo will send the cost estimate by Friday. The team wants to discuss budget next week.” Our deliverable is an email that confirms explicit actions and asks about the gaps.
Anthropic’s prompt-chaining pattern describes dependent model calls with checks between them. You can use the same pattern manually in a chat before building an automated integration.
Request 1: extract an evidence table
Extract assignments from these notes.
Return action, owner, due date and supporting quotation.
Keep proposals separate. Mark missing values as not specified.
Do not draft an email yet.
Notes: Maya will draft the proposal.
Leo will send the cost estimate by Friday.
The team wants to discuss budget next week.Example handoff artifact
| Type | Action | Owner | Due date | Evidence |
|---|---|---|---|---|
| Assigned | Draft proposal | Maya | Not specified | “Maya will draft the proposal.” |
| Assigned | Send cost estimate | Leo | Friday; exact date unresolved | “Leo will send the cost estimate by Friday.” |
| Proposed | Discuss budget | Not specified | Next week; exact date unresolved | “The team wants to discuss budget next week.” |
Gate 1: approve the facts
Compare each row with its quotation. Stop and correct any invented assignment or transferred deadline. Unknown dates may pass only when the next stage is explicitly allowed to ask about them. They cannot pass into calendar scheduling as resolved dates.
Request 2: draft from the approved artifact
Use the approved table below to draft an internal follow-up email
under 120 words. Confirm assigned actions. Ask for Maya's due date,
the calendar date for Friday, and an organizer/date for the proposed
budget discussion. Do not turn the proposal into an assignment.
Return a draft only.
Approved table: [paste the reviewed table from Request 1]Example email
Subject: Proposal and estimate follow-up
Hi team,
Maya will draft the proposal, and Leo will send the cost estimate by Friday. Could we confirm Maya’s due date and the calendar date for Friday?
The budget discussion is proposed for next week. Who will organize it, and which date should we use?
Thanks.
Gate 2: review before acting
The email preserves the two assignments and leaves the proposal open. Check recipients and dates, then approve the message before sending. Keep the input, approved table, draft and corrections together. If a source changes, repeat extraction and review before reusing the draft.
More stages add time and review work. Use them where an intermediate check can catch a meaningful error. For a single missing detail in a draft, one bounded revision may be sufficient.