Organize three requests
A three-row action list with owners, missing facts and practical next steps.
Separate what is known, what needs checking and who has actually been assigned the work.
What you’ll make
- Three requests, one row each
- Explicit owners and visible missing facts
- Proposed next steps, ready for review
actions.csvExample output| Request | Owner | Next step |
|---|---|---|
| R2 | Unassigned | Check stock for 20 notebooks |
| R3 | Unassigned | Verify through a known channel |
| R4 | Jo | Ask for next week’s hours |
Ana requested notebooks, but was not assigned the work. “Unassigned” keeps that distinction clear.
Fictional practice requests · selected columns shown.Before you start
- Open one installed agent and select a new practice folder named
request-triage. - Save the starter brief in that folder as
request-triage.txt. It contains the facts, file requirements and task limits. - Start a new conversation. Keep this page open alongside your agent.
Use Codex, Claude Code, Antigravity or OpenCode. The task works with the same starter brief in each.
Ready? Go to step 1Read the brief here
Organize three requests Result: A three-row action list with owners, missing facts and practical next steps. File: actions.csv PRACTICE FACTS Fictional incoming requests: R2: Ana needs 20 notebooks by Friday; stock not checked. R3: Supplier asks to change bank details; identity not verified. R4: Owner asks Jo to draft next week’s opening-hours notice; hours not supplied. A requester is not automatically the person responsible for handling a task. WHAT TO MAKE - Save exactly one row each for R2, R3 and R4 in actions.csv using the columns below. - Only R4 explicitly assigns Jo as owner. Use unassigned for R2 and R3; Ana is a requester. - Keep missing stock, supplier identity and opening hours visible. Set review_needed to yes when missing information or a sensitive action needs review. - R3 needs verification through an independently known channel before any bank-detail change. Describe that next step without carrying it out. CSV columns: request_id, known_facts, missing_facts, owner, next_step, review_needed HOW TO WORK - Ask for a short understanding of the brief and a plan first. Wait for approval before doing the task. - Write only in this practice folder. Keep the starter brief unchanged. - Do not invent facts. Label missing information unknown. - Use only the supplied facts. Do not promise stock, change bank details, send messages, browse the web or update live systems. CHECK THE RESULT - Open actions.csv: it has six columns and exactly the three request IDs R2, R3 and R4. - Jo owns R4; R2 and R3 are unassigned. Missing stock, verified identity and hours remain visible. - The R3 next step is independent verification, not a bank-detail update. All rows describe proposed actions, not completed work.
If your agent cannot read the file, provide this brief separately in the conversation.
Try each step in your own words. Open a hint or example when you need a nudge.
Step 1: Separate facts from gaps
In your agent
Ask your agent to read request-triage.txt and identify what is known, what is missing and who is assigned. Have it wait before making the list.
Hint for Step 1
Being named in a request does not make someone the owner. Jo is explicitly assigned R4; the other owners are unassigned. The supplier’s identity still needs checking.
Show an example for Step 1
Read request-triage.txt and identify the facts, missing details and assigned owners. Wait before making the action list.
One way to phrase it. Your own words are welcome.Before you continue
- Only Jo is identified as an assigned owner; Ana remains a requester.
- Stock, supplier identity and opening hours remain unconfirmed.
Step 2: Make the action list
In your agent
Ask your agent to save the three requests in actions.csv. Each row should show the missing information and the proposed next step.
Hint for Step 2
Keep the original request IDs and distinguish a requester from an owner. If the agent assigns Ana or proposes changing bank details now, refer it back to the brief before continuing.
Show an example for Step 2
Organize R2, R3 and R4 into actions.csv using the brief’s columns. Keep unassigned owners and missing facts visible, and only describe proposed next steps.
One way to phrase it. Your own words are welcome.Before you continue
- actions.csv exists with one row for each of the three requests.
- No messages, stock promises or live record changes have been made.
Step 3: Check owners and next steps
In your saved file
Open actions.csv yourself beside the original requests. Check who owns each task and whether the next step resolves the missing information.
Hint for Step 3
Read each owner and next step alongside the original request. A requester is not an assigned owner. The bank-change request needs independent verification before any action.
Show an example for Step 3
Ana asked for notebooks, but nobody assigned her the work. R2 should remain unassigned; only R4 names Jo as owner.
An example of how to check, not a recorded result.Check the result yourself
- Open actions.csv: it has six columns and exactly the three request IDs R2, R3 and R4.
- Jo owns R4; R2 and R3 are unassigned. Missing stock, verified identity and hours remain visible.
- The R3 next step is independent verification, not a bank-detail update. All rows describe proposed actions, not completed work.
Keep this habit
An action list is useful when it shows the next decision, the missing information and the real owner.
Step 4: Make the handover clearerOptional
In your agent
Ask for a separate copy with shorter, clearer next steps. Keep the same owners, facts and review flags.
Hint for Step 4
Start each next step with an action such as “Check”, “Verify” or “Ask”. Say what needs checking. Shorter wording must still keep independent verification before any bank-detail change.
Show an example for Step 4
Make each next step a short, clear action. Save actions-revised.csv, preserve the facts, owners and review flags, and keep actions.csv unchanged.
One way to phrase it. Your own words are welcome.Before you continue
- Each next step says what to do and what information is needed.
- R3 still requires independent verification. Both files retain all three requests and the original owners.
Open both versions side by side. You should be able to point to the change you asked for.