Dako's AI Builder Notes
System
Color theme
Changsha HubOffline
大可 Dako
大可 Dako大可 DakoAI Builder · Agent PractitionerTurning AI into working software. Practical notes on agent engineering, vibe coding, and commercial delivery.
Platform links coming soon
Using a product starts by changing how you hand work overA questionYou want an explanation, an idea, a replyYou get a chatIt ends when you nodAn assignmentYou want a file, a table, a changeYou get a deliverableYou check it against the briefOnly a deliverable can be accepted; chat can only continue
If you only hand over a question, you only get a reply.

Stop Asking. Assign the Work.

Chat returns a paragraph. An assignment returns a finished artifact you can accept. Switch that first.

Chat products and work products share a text box. The handoff is different. Ask “what should I do this week” and you get advice. Say “write the weekly update from these two notes, save it as a file, and every number must recompute from the detail rows” and you get something you can turn in.

After reading, you should be able to answer:

  • What comes back from a question versus an assignment?
  • Why does a smooth chat not mean the job is done?
  • After you change the handoff, which part do you still own?

What you are actually handing over

A question wants understanding. Once the reply makes sense, the thread is over. An assignment wants delivery: a file in a named place, a change in the repo, a spreadsheet you can open. xAI calls these teammates that do real work; OpenAI describes Codex as starting from a goal, taking action, and producing something useful. Different wording, same test: you should get an artifact, not the next paragraph.xai-bot codex-overview

A blunt check: close the window. What is still on the desk? A file, a commit, a draft waiting for send — that was an assignment. A paragraph you already read — that was a question.

Smooth chat is not done

People stall here. The product answers fast, the tone is right, so they think they know how to use it. They only know how to ask. The real cut is acceptance: check the result against a brief you wrote before it started. Without that, you can only say “looks fine,” and the next similar job starts from zero.

That is why this section does not teach install screens. Chrome changes every week. The handoff still holds in six months: you want a deliverable, the process has to be visible, and the result has to be checkable.

You still steer

Assigning work is not assigning judgment. Goals, tradeoffs, irreversible acts, numbers, and anything that leaves the building stay yours. The human boundary already draws that line: execution can speed up; judgment cannot be outsourced. A stronger product only rows faster. It does not pick the heading.

Next, write the assignment so it can be checked: five things every assignment needs. If you have not picked a product yet, start with match the product to the work.

References

  1. Grok Bot — xAI
  2. Codex documentation