You will leave with a reusable assignment format for tools, collaborators, contractors, and your future self.
Powerful tools reward clear direction. Vague requests produce vague output. Context, boundaries, examples, and review make help usable.
Do not ask for output. Assign work.
Most people use new tools like search boxes: they type a vague request and hope the answer is good. Five Days Forward teaches a different habit. You create a work order.
A work order names the mission, relevant context, constraints, desired output, examples, risks, and acceptance criteria. The same pattern helps with software, research, writing, planning, design, hiring help, asking a friend for feedback, or using an AI assistant.
Protect the private layer.
The more context a tool receives, the more useful it may become. That also creates privacy and judgment risk. The rule is simple: classify before sharing. Remove secrets, account numbers, private family details, medical details, legal details, and anything that would create harm if stored or repeated.
For sensitive work, use summaries, fictionalized details, local tools, or human professionals. The point is not fear. The point is adult supervision of powerful leverage.
Every helper needs a standard.
A tool can draft faster than you can think. That is useful only if you know how to judge the draft. Day Three builds the review criteria before the output arrives.
The strongest participants do not treat generated work as truth. They compare it against the mission, constraints, facts, tone, ethics, and usefulness. They ask what is missing, what is weak, what is risky, and what should be tested.
Create the Five Days Forward work order
- Write the mission in one sentence.
- Add only the context a helper needs to understand the task.
- List constraints: time, money, tone, privacy, tools, audience, quality bar, and what not to do.
- Define the output format: checklist, draft, plan, script, code, outline, table, email, research brief, or prototype spec.
- Write acceptance criteria: how you will know the output is usable.
Use the work order template
This is the central technology lesson. It works for AI assistants, human collaborators, contractors, and future-you.
Mission: blank.
Context: blank.
Constraints: blank.
Output I need: blank.
Examples or references: blank.
Quality bar: blank.
Risks to avoid: blank.
Before finalizing, critique your own answer against the quality bar.
How to know you are doing it right.
- A vague prompt is not a plan.
- Context is useful only when it is relevant and safe to share.
- The review criteria matter as much as the request.
- Ask for critique before you ask for polish.
Before moving on.
- I have a reusable context package.
- I have one clear work order for my Day Five proof.
- The work order includes constraints and acceptance criteria.
- I know what private details I will not paste into external tools.