Single track · 7 short lessons
The direct version: the same seven topics as OSWork, with the diagram doing the explaining and the text simply tying it together. Ten minutes per lesson. No programming, no command screen.
Lessons
Leave knowing how to turn a vague question into a request that comes back ready to use.
Leave knowing how to check an answer in two minutes, with three written items before you ask.
Leave with a real folder set up for your work front — and with what never goes in there.
Leave with your rules written down once, instead of repeating them with every request.
Leave with the request for your most repeated task saved and ready, so you swap only what changes.
Leave knowing how to change a material with a guaranteed return point to the previous version.
Leave with the full workspace set up and your written delegation list.
Track 01 · Lesson 1
At the end of this lesson, you turn a loose question into a complete request — material, output, definition of done — and you get something ready to use.
The rework hits late afternoon: a text to redo completely. The cause is what you left out when you asked.
↓ scroll to study
In a new conversation, nobody on the other side knows your school or your team. The system reads only the box. The rest it fills in using the average.
What goes with it has a name: context. It’s the raw material of the work.
A teacher asks “summarize yesterday’s lesson” and gets a text that works for any class. It didn’t use the plan, and it didn’t say the grade level.
In the workshop, the work order records the noise level, what to solve, and the deadline. A request to the AI carries the same.
Material: what it reads. Output: length, tone, reader. Definition of done: what needs to show up.
A manager pasted a thirty-page rule, asked “table: topic, teaching hours, audience, and month” and closed with: “ready as long as it covers the five topics.”
Before
“Build a schedule based on this rule.”
After
Rule pasted · four columns · five topics.
Balance: four rewrites turned into an adjustment.
The definition of done stays in your head — and what stays only there doesn’t make it to the other side.
“It’s good” is a wish. “Cite three decisions” is a definition: count three, or it doesn’t count.
A history teacher corrects eighty returns per grading period with one definition: one correct, one improvement, up to four lines. Check each one in seconds.
Test yourself
You asked for “a piece of material about the new rule”; a correct text came that nobody used. What was missing?
Close the request with one line: “before you run, tell me what’s missing”. It takes thirty seconds.
Go back with a short, uncomfortable list: audience, deadline, original text. What you’d discover later comes first.
A manager used the line before the reimbursement rule notice went out. The AI asked which month it was valid from and who would be covered. Two things were missing.
The AI can’t guess what you didn’t write.
Practice now 0/3 done
Ready when the answer comes back without a rewrite. About 5 min.
Nothing here leaves your conversation. If it sounds weird, delete it and send again.
MATERIAL <copy the material> OUTPUT Format: <up to 10 lines> DEFINITION OF DONE It is only done if: <cite the 3 decisions> Before you run it, tell me what is missing.
Complete request, ready answer.
Summary
Track 01 · Lesson 2
By the end of this lesson you can check an AI answer in under two minutes, using a three-item ruler that you write yourself before you ask.
The wrong answer arrives with the same tone as the right one. Without an annotated list first, you check by the feeling that it’s well written.
↓ scroll to study
The AI chooses the most likely word. Without material, it fills the gap with something plausible, in the same firm sentence.
A geography teacher asked for a paragraph about a river. Correct kilometers; the flood year swapped with two.
Test yourself
Two well written answers disagree. What fixes it?
Before the request, write down the checking ruler. One, the bait you know by heart. Two, the numbers that match. Three, what must not appear.
A manager was going to build the vacation board. She noted her balance, the dates to match the spreadsheet, and nothing outside the document.
Before
Reread everything and send.
After
Three lines before the request.
Balance: from eight minutes to two.
Tools change screens, name, and price. The way you build the sentence doesn’t change. Your ruler doesn’t get old.
A literature teacher switched tools. The new one listed a title that that author never wrote. Item two caught it: library catalog.
The ruler solves what can be checked: number, name, date. The consequence for someone’s life no list covers. Check, and keep to yourself the sentence that affects a person.
A manager organized the semester absences. Correct numbers. The paragraph that suggested dismissing someone she erased.
Confidence in tone is not proof of anything.
Practice now 0/3 done
Ready when it matches the answer key. About 6 min.
Fictional case, on this page: nothing is sent or saved. Getting it wrong is the goal.
Sílvia coordinates support for a school. She pasted a proposal into two tools and asked for a summary. One invents a condition.
PROPOSTA Aurora · 3 visits per week · R$ 4.200 per month 12 months · annual adjustment TEXT A 3 weekly visits, R$ 4.200 monthly, 12 months, adjustment annual. Includes 2 extra visits per quarter. TEXT B 3 visits per week, R$ 4.200 per month, 12 months, annual adjustment.
Fail: the A. The extra visits aren’t in the proposal, and that’s what makes it most complete.
Item: the third one. The numbers match; only the ban on citing what wasn’t delivered brings the sentence down.
Sílvia: use the B, or delete the sentence. Check the proposal, not the tool.
Two checked answers against the source, with a written checking ruler beforehand.
Summary
Track 01 · Lesson 3
At the end of this lesson you have one folder in front of your work, with what the AI needs to read. And you know what never goes in there.
Your material is scattered: email, desktop, old attachment. That’s why you re-explain everything in every conversation. You’re missing one single place.
↓ scroll to study
Folder here is the common folder on your computer. I call it in front of your work a topic that comes back every week. Each in-front-of-your-work gets its own folder, cut by the topic, not by type.
A manager created the folder “junior analyst hiring”: the opening, interview questions, and salary table. Before, each piece lived loose.
What you would explain out loud to whoever took over tomorrow: source material, an example of a good result, rules of the place, and the decision made.
A math teacher put together the recovery folder: the contents charged for, a corrected test, and the rule for the minimum grade. Each exercise comes out at the right level.
Common mistake
Put everything in there and expect the AI to choose. It reads twenty versions with the same weight and answers for the wrong one.
The folder can be read outside your home. Never go in: another person’s document, address, health data, account, and password. If the material only works with names, use nicknames: Student A.
A manager kept the team evaluation only in the copy with Collaborator A, B, and C, with no document or salary.
Every living folder together breeds clutter: yesterday’s version becomes today’s wrong one. Reserve ten minutes at the end of the month, always the same sequence.
A biology teacher does this on the last Friday, in the science fair folder: she took out two expired rules and pulled the invitation sent for “old”.
The ten-minute cleanup
Practice now 0/4 done
Ready when a single folder shows the three materials that explain the front. About 6 min.
Nothing is deleted. Moving doesn’t destroy: the file leaves one place and appears in another. If it looks wrong, the computer undoes the last move.
One front, all in one place.
Summary
Track 01 · Lesson 4
At the end of this lesson you have an orientation sheet written for one of your work fronts, which saves you from repeating your rules with every complete request.
You repeat the same requirements in every new conversation. On a regular day you forget one, and the text comes out wrong.
↓ scroll to study
Who covers your vacation gets a paper with the house combinations. The orientation sheet is that paper, for a work front.
It lives in the folder and goes into every new conversation. Plain text, in Portuguese; tech teams call it AGENTS.md.
A purchasing manager repeated two requirements: supplier by legal name, deadline with a date. She wrote both lines once.
Common mistake
Fill in the materials sheet. Sheet pasted: the sheet swells, and the rule gets lost.
A good sheet isn’t a long sheet. Who reads sets the tone. How I write keeps your mark. What never shows up is the limit. When it’s ready, the definition of done.
Answer with something verifiable: “be clear” can’t be measured; “up to twenty words” is counted.
A science teacher made the agenda reminder sheet. Who reads: busy guardians. Never: student name. Ready: one paragraph with the date.
Lines copied from one sheet to another are general rules: they get their own sheet, above the folders.
The project rule stays on the folder sheet and, at the crossing, it wins: it’s the closest to the work.
A manager’s general rule: the number always has a source. Only in the directorate report: compare with the same month from last year.
Separating layers
The group changes, the directorate asks for another format; the sheet stays the same, forcing a way that’s already gone.
Write the revision date on the first line and refer back to it when the work changes. Old rule goes out.
A teacher made the recovery sheet in March, morning group. In August, night group, “reading for tomorrow” became impossible.
Test yourself
Three months later, the answers bring a treatment the team abandoned. Why?
Practice now 0/3 done
Ready when you answer the four questions on one screen, with no pasted material. About 6 min.
Your text, on your computer; nothing leaves it unless you attach it.
Swap only what’s between the signs.
CARD — <front> Reviewed on: <date> WHO READS <e.g.: sixth-grade guardians> HOW YOU WRITE <e.g.: short sentences> NEVER APPEARS <e.g.: student name> READY WHEN <e.g.: one paragraph with a date>
Sheet ready.
Summary
Track 01 · Lesson 5
At the end of this lesson, you have a request template saved for the task you repeat most in your month—ready to use by changing only what changes.
Every week you rewrite the same request: a calm Tuesday delivers well; a rushing Friday comes out halfway. Fix it once.
↓ scroll to study
A task comes back the same in form, different in content. A template is this request written once, on a calm day. You open it, swap what changes, and send it.
Every Friday, a manager builds the indicators report for the board. Only the numbers change: forty rewrites per year.
Common mistake
Keep the good answer, not the request that produced it. The text serves one case; the recipe serves all.
Mark each line from the last real request: always or only this time? The fixed part stays in full; what changes becomes a blank with an example.
A teacher builds the recovery list by term. Fixed: twelve questions with the answer key. Blank: the content and the two most common mistakes.
Test yourself
Same template, two answers with different length and tone. Cause?
Template only with material and format saves typing, not checking. Write inside it what the answer needs to have and what it can never miss.
A manager responds to complaints from the site. Required: repeat the problem using the customer’s words and give a deadline. Prohibited: promise a refund. Checking: twenty seconds.
Building your template
A template you can’t find in ten seconds is a template with no use. It lives in the front work folder, next to the form, named by the task: “template — weekly report”.
A teacher saved “template — recommendation letter” in the school folder. A complete request arrives: you open it, change the name and period, deliver it on the day.
Practice now 0/3 done
Done when two pieces of content return the same size and tone. About 6 min.
Nothing leaves your computer. The template is your text: delete or rewrite it whenever you want.
“Write once”: fill it in today and leave it. “You change this”: fill it in each time you use it.
TEMPLATE — weekly report FIXED (always) Tone and size: <write once — e.g.: direct, 12 lines> GAPS (change each time) Material: <you swap this — paste the text> Period: <you swap this — e.g.: 6 to 10/10> CRITERION (always) Ready if: <write once — e.g.: 4 numbered indicators> Never: <write once — e.g.: a number outside the material>
Your template returns the same pattern on any day.
Summary
Track 01 · Lesson 6
At the end of this lesson, you change a material while knowing how to go back to the previous version, without relying on memory.
You improve one detail in the sheet; the week turns out worse — and when you undo it you discover you saved over the good version.
↓ scroll to study
Changing a rule that already works is a bet: you fix one detail and ruin another, silently. The problem isn’t betting — it’s betting without a return point.
A manager changed the time-off rule on the schedule. Two weeks later, two Saturdays were empty — and the old version had already been saved over.
Before
Open, change, save. The good version disappears.
After
Duplicate with the date, change in the original, save. Both exist.
Balance: fifteen seconds per change, instead of rewriting for half an afternoon.
Before changing a material that works, duplicate the file and put today’s date at the beginning of the name. The copy stays frozen.
From the biggest to the smallest date: year, month, day — the folder sorts itself.
A math teacher duplicated the sheet before easing the minimum grade. It became too soft; he opened the copy and put the phrase back.
The two files side by side show which phrase came in and which one went out. Nobody keeps the reason — and without it you undo a good decision.
One line per change: date and reason, in the same place.
A manager’s note: “I removed the estimated value from the minutes because two suppliers received it by mistake.” Months later, she answered what no one remembered.
The material shows what changed. Only you keep the why.
The same notebook records the failures: date, what went wrong, the smallest fix. On the day — by the end of the month it’s already gone.
In ten lines, the pattern shows up: you correct the rule, not the result of the day.
A science teacher noted a month of failures in a lab worksheet. Three lines asked for the warning about the heated material: it became a requirement on the sheet.
Test yourself
You changed a rule and the result got worse. You have the dated copy, but you didn’t write anything. What did you lose?
Practice now 0/4 done
Ready with the dated copy, the modified sheet, and the reason line. ~5 min.
You don’t erase anything — the first step is to duplicate. If it doesn’t feel right, open the copy and go back.
You changed a material with the previous version saved and the reason noted.
Summary
Track 01 · Lesson 7
At the end of this lesson, you have the setup ready and a written list of what you delegate, what you check, and what keeps on you.
You still need to decide where the delegation ends. Without a written line, it gets drawn on a full day, on the wrong side.
↓ scroll to study
Every task has two parts: producing and answering for the result. The AI takes the first. The second keeps on you.
It’s the supervised delegation: you hand over the doing and you hold the answering.
A customer service manager sent the monthly report without reading the last table, which swapped reopened items for resolved ones. She was the one who explained the mistake in the meeting.
Does it alone: accepts without looking. Does it and shows: goes through your eyes before moving on. Just suggests: you do it, with the answer as a draft. The level comes from the cost of the mistake, not the tool.
A biology teacher: a review list—does it and shows; a bulletin board notice—in does it alone; a test—in just suggests.
Three questions to classify
The simple math: it used to take forty minutes, then it took one, and thirty-nine were left over. You still need to check.
The honest calculation adds up the request, the check, and the adjustment. If it gets close to the time you have on hand, the delegation only changes the effort from one place to another.
A operations manager delegated the vacation schedule: setting it up took twenty minutes, checking it took eighteen. She picked up the schedule again and delegated the email.
The list ages because you get better at asking. A task goes up when it’s proven, and goes down when it fails twice. Fixed time on the calendar: fifteen minutes per week.
Rosana, a manager of a scheduling service, set up a folder, an orientation sheet, and a template in one month. In the fourth week, the notice went out with an expired deadline, and the dated copy sent back returned the good version in two minutes. The noted line, the deadline changed—and the sheet didn’t. It opened the next check.
A geography teacher scheduled the check for Friday, 4:00 PM. In four weeks, two tasks went up and one went down.
Complete request, checking ruler, folder up front, orientation sheet, template and dated copy: six habits. Together, under the delegation list, they become an environment you explain in five minutes.
A project manager delivered the folder, sheet, and template on the new person’s first day. The onboarding took three days, not two weeks.
Apply it to your case
Practice now 0/4 done
Ready when this week’s tasks are in the three columns and the check has a day and time. About 7 min.
The list is yours and it doesn’t go anywhere. Moving a task from a column is a sign that it works.
Environment set up, list written: you know what you delegate, you check, and you keep going.
Summary