侠Liangshen AIailiangshen.com
AI Implementation Course · Short topic lessons · Lesson 1

One Sentence to Hand Over Weekly Repetitive Tasks to AI

Ask Three Questions First, Then Solidify into a Process

Freeabout 9 minNo experience neededWeb lesson + slides + video

This lesson covers only one thing: how to give instructions so it doesn't have to listen to you from scratch every time. The method is simple: state the task clearly in one sentence, have it ask you three questions first, and then solidify the results into a process document.

By the end of this lesson, you can

  • Clearly state a weekly repetitive task in one sentence
  • Have it ask you three questions first, then write a process document
  • Test run with three examples and calculate a baseline

Takeaway: A process document under 300 words, plus a baseline

01

Opening and Scenario

About 2 minutes

A task done weeklyFictional example, numbers are illustrative

Yuanfan Technology · Administrative Specialist Lin Yue

Every Friday afternoon, she needs to compile a summary of store purchase requests for the week, taking about 40 minutes each time.

She tried directly saying: Help me organize the purchase requests. The format was different every time.

The issue isn't with the AI, but with how you instruct it. Have it ask first to clarify the rules.
02

Method

About 3 minutes

Method: Four Steps

Do it yourself firstKeep the original materials and the final product you created by hand as examples
→
Explain in one sentenceI perform a specific task weekly: the input is [materials], and the output is [finished product].
→
Ask it three questions firstAsk all three questions at once, and answer them all at once.
→
Standardize into a process documentSave it as a fixed document so you can copy and paste the entire section next time.
One-sentence format: I perform [task] weekly. The input is [materials]. The output is [product].

Test with three examples, then calculate the cost

1
One normal example
2
One example with missing information
3
One example with messy formatting
If something is wrong, modify the process document, not just the result of this single instance.

Poor instruction vs. good instructionThe same task, described in two ways

Poor writing

Help me handle the procurement.

After reading this, a stranger would not know what to do.

Good writing

Every Friday, I need to consolidate scattered procurement requests from various departments into a summary table containing four columns: applicant, item, amount, and date.

The input, output, and format are all clearly specified.

After reading the good writing, a stranger can get started.
03

Prompts and Examples

About 2 minutes
Tip

Part 1: Ask it to ask you questions first

Suggested time Approx. 1 minute
Prompt 1
I perform a repetitive task weekly: [Task name, e.g., Consolidate this week's procurement requests].
The input is: [What the raw materials are, e.g., scattered application messages from various departments].
The output is: [What the final product is, e.g., a summary table].
Please do not start working yet. First, ask me three critical questions to help you understand my rules.
List all three questions at once, numbered. Provide your guessed default answer after each question. I will only need to confirm or modify them.
It first asks three questions and provides default answers; if it starts working directly, ask it to stop first.
Tip

Part 2: Save as a process file

Suggested time Approximately 2 minutes
Prompt 2
Thank you. Based on our Q&A, please write a 'reusable process file'.
Requirements:
1. Start with the four-layer script: who (role, years of experience, service target) and thinking style (what to look at first, how to draw conclusions).
2. State working principles, such as output length, order, conclusions first, and stating uncertainty directly.
3. List precautions, such as boundaries not to cross and not to draw conclusions.
4. List processing steps with numbers and specify the output format.
5. Specify 'what to do when materials are missing': mark it, do not guess.
6. Keep the entire text under 300 words; I will copy the whole paragraph to you next time.
Use only the content you provide; write 'to be supplemented' for missing parts; do not fabricate or make promises on my behalf.
The entire text must not exceed 300 words; the item 'what to do when materials are missing' must be retained.

Input: Three scattered purchase requestsFictional example, numbers are illustrative

Three original messages

Message 1 (Store A): Wants two boxes of A4 copy paper, 180 per box, needed before Thursday, applicant Xiao Zhou.

Message 2 (Store B): 10 cash register ribbons, needed Friday, applicant A Jie. (No amount reported)

Message 3 (Headquarters): 3 bags of coffee beans for the pantry, 68 per bag, needed next Monday, applicant Colleague C.

Note Message 2: No amount. It should mark it, not guess.

Expected output: The missing cell is marked

1
Xiao Zhou: A4 copy paper 2 boxes360 yuan (180 * 2, calculated from unit price, please verify); before Thursday (specific date to be supplemented)
2
A Jie: Cash register ribbons 10 unitsAmount to be supplemented (no amount reported in message); Friday (specific date to be supplemented)
3
Colleague C: Coffee beans 3 bags204 yuan (68 * 3, calculated from unit price, please verify); next Monday (specific date to be supplemented)
Total 564 yuan, excluding the 'to be supplemented' line. Confirmation needed: A Jie's ribbon amount.
04

Practice and Self-Assessment

About 2 minutes

Five-minute mini exercise

1
Use three purchase requests, fill in the first prompt, and have it ask three questions
2
Accept default answers directly, only adding one: mark the line missing the amount, do not guess
3
Have it write a process file under 300 words, copy and save
4
Start a new conversation, paste the workflow document and the three applications, and compare them with the expected output.
Check the standard: the amount in the second line should be marked as 'pending supplementation' rather than having a number filled in for it.

Done: self-evaluated on four criteria, passing with three points.

This method is suitable for tasks that are repeated weekly or monthly; where inputs and outputs have a fixed format; and where the cost of errors is low, or someone oversees the final step. For one-time tasks, just ask directly.
Show the full transcript (video narration)
One Sentence to Hand Over Repetitive Tasks

Welcome to Mini-Course P01: One Sentence to Hand Over Weekly Repetitive Tasks to AI. This lesson covers only one thing: how to give instructions so it doesn't have to listen to you from scratch every time. The method is simple: state the task clearly in one sentence, have it ask you three questions first, and then solidify the results into a process document.

After completing this section, you will be able to

After completing this section, you will be able to do three things. First, clearly state a weekly repetitive task in one sentence. Second, have it ask you three questions first, then write the results into a process document. Third, test run with three examples and calculate a baseline. You will take away a process document under 300 words, plus a baseline.

A task done weekly

Here is an example, which is fictional, with numbers for illustration. Administrative Specialist Lin Yue needs to compile a summary of store purchase requests for the week every Friday afternoon, taking about 40 minutes each time. She tried directly telling it: Help me organize the purchase requests. The results varied widely, with different formats each time. The issue isn't with the AI, but with how you instruct it. It doesn't know your rules or what you expect when it first receives your request. Instead of adding details repeatedly, it's better to have it ask you first to clarify the rules, then solidify them into a reusable process.

Method: Four Steps

The method has four steps. Step 1: Do it yourself first. Keep a copy of this week's raw materials and the finished product you created by hand; these are your examples. Without having done it yourself, you cannot clearly define the acceptance criteria. Step 2: Explain the task in one sentence using the format: I perform [task] weekly. The input is [materials]. The output is [product]. Step 3: Ask it to ask you three questions first; do not rush to start working. Ask all three questions at once, and answer them all at once. This is far more efficient than ten back-and-forth exchanges. Step 4: Ask it to write the Q&A results into a process document and save it as a fixed file, so you can copy and paste the entire section next time.

Test with three examples, then calculate the cost

Step 5: Test with three examples: one normal, one with missing information, and one with messy formatting. If anything is wrong, ask it to update the process document rather than just fixing the result of this single instance. Step 6: Calculate the cost: compare the time before versus now. Use arithmetic, not vague adjectives like 'much faster,' and record the baseline: time per instance, frequency per week, and the most common error. Many applications refer to such reusable operating manuals as 'skills.' The name may vary, but the method is the same; check the name and entry point in your current version.

Poor instruction vs. good instruction

Compare the two descriptions. Poor writing: 'Help me handle the procurement.' Good writing: 'Every Friday, I need to consolidate scattered procurement requests from various departments into a summary table containing four columns: applicant, item, amount, and date.' The good writing includes the input, output, and format, avoiding vague terms like 'organize' or 'handle.' After reading it, a stranger can get started.

Part 1: Ask it to ask you questions first

Use the first prompt at the beginning. Replace the content in the brackets with your specific task, input, and output, then send it. It should first ask you three key questions, each followed by its guessed default answer. You only need to confirm or modify. If it starts working directly, ask it to stop and only ask questions.

Part 2: Save as a process file

Part 2 prompt: solidify the Q&A into a process file. It has six requirements: clearly state who and thinking style in the four-layer script at the beginning; state working principles; list precautions; list processing steps with numbers and specify output format; specify what to do when materials are missing, mark it, do not guess; keep the entire text under 300 words. Use only the content you provide; write 'to be supplemented' for missing parts; do not fabricate or make promises on your behalf. After writing, save it, and copy the whole paragraph to it next time.

Input: Three scattered purchase requests

Using three scattered purchase requests for a test run is fictional, and the numbers are illustrative. Message 1: Store A wants two boxes of A4 copy paper, 180 per box, needed before Thursday, applicant Xiao Zhou. Message 2: Store B wants 10 cash register ribbons, needed Friday, applicant A Jie, no amount reported in the message. Message 3: Headquarters wants 3 bags of coffee beans for the pantry, 68 per bag, needed next Monday, applicant Colleague C. Note Message 2: no amount. It should mark it, not guess a number.

Expected output: The missing cell is marked

The expected output is a summary table. Xiao Zhou's A4 copy paper, 2 boxes, 360 yuan, calculated from unit price, please verify; date before Thursday, specific date to be supplemented. A Jie's cash register ribbons, amount to be supplemented because no amount was reported in the message; date Friday, specific date to be supplemented. Colleague C's coffee beans, 3 bags, 204 yuan, calculated from unit price, please verify. Total 564 yuan, excluding the 'to be supplemented' line. What needs confirmation is A Jie's ribbon amount. Note the second line: the line missing the amount is marked, not guessed. This is how the rule 'mark when missing' takes effect.

Five-minute mini exercise

Now, do a five-minute mini-exercise. Using the three procurement applications above: First, fill in the brackets of the initial prompt with 'Procurement Summary' so it asks you three questions. Second, accept its default answers directly, but add one rule: rows missing amounts must be flagged, not guessed. Third, have it write a workflow document under 300 words, then copy and save it. Fourth, start a new conversation, paste the workflow document and the three applications, and compare them with the expected output. The same applies to the tech industry version: Jiang Haoran, a full-stack test engineer at Heyao Electronics, writes defect daily reports every day. Common issues include missing reproduction steps and duplicate tickets for the same problem. He also starts by having it ask three questions, then solidifies the result into a workflow document.

Done: self-evaluated on four criteria, passing with three points.

Final self-evaluation. Record one point for each criterion met, with a maximum of four points. Three points or more is considered passing. First, the prompt includes inputs, outputs, and formats, without vague terms like 'organize it' or 'handle it.' Second, the workflow document states 'flag missing materials, do not guess,' and samples with missing information were indeed flagged. Third, the numbers in the baseline were recorded by timing yourself, not estimated. Fourth, after errors occur, you update the workflow document, rather than just fixing this single instance. To use this method, a task must meet three criteria: it is repeated weekly or monthly; the format of inputs and outputs is relatively fixed; and the cost of errors is low, or someone oversees the final step.