Skip to main content

Writing a request that comes back right

Lesson 2 of 10 · 3 min 44 s. Write a request that comes back as you pictured it. Attach a sketch, list what finished means as a checklist, say what to leave alone and set whose task it is and how urgent, then read the report checking every item and see the result beside the sketch.

Before you start​

  • You have done Your first task and are signed in to the console.
  • You have a project you can start tasks in, and a rough sketch of the screen you want as an image file. The lesson uses TimeSaver, a time-tracking app for small teams.

Steps​

  1. Open the new-task form in your project and start with what you want, in your own words. The lesson's request is: Add a calendar to the top of the Reports page that shows the past four weeks day by day, so I can see which days we tracked time and how much.
  2. Click Attach, under the description, and choose your sketch. It now sits under the description as a file that goes to the agent with the request, so the agent builds to the picture as well as to your words. One rough picture is enough.
  3. Say what finished means. On a new line, write It's done when:, then click Checklist in the editor's toolbar and put one item on each line. The lesson's items are: four rows of seven days, Monday to Sunday, ending with this week; each day shows its hours; busier days are shaded darker; today is outlined; it matches the attached sketch. The agent checks every item before it hands the work back, and its report says how.
  4. Press Enter twice to leave the checklist, then say what the agent must leave alone. The lesson's line is: Leave the other reports and the week controls as they are, and don't add any libraries. A line like this keeps a small change small, because an agent that notices something worth improving on the way would otherwise improve that too.
  5. Open Advanced, below the controls, to see whose task this is and when it's picked up. Assigned to, beside Attach, starts as you; give the task to a colleague and it follows them instead, in their list and their questions. Priority decides what is worked on first when several tasks are waiting their turn. The lesson leaves Priority at Normal and the task assigned to you.
  6. Choose Unattended and press Go. The task appears on Tasks and waits its turn, like any other.
  7. When it's finished, open the task and go to Artifacts, where the agent's report is. It goes through what you asked for, item by item, each with how it was checked and the evidence beside it. That is the answer for anyone who asks whether the change does everything it should, before anyone reads the code.
  8. Compare the result with your sketch. In the lesson, TimeSaver's Reports page shows four weeks of days, Monday to Sunday, each with its hours, the busy days darker and today outlined, above the reports that were there before.

What you learned​

  • A request comes back as you meant it when it says what you want, shows it with an attached sketch, lists what finished means as a checklist, and says what to leave alone.
  • All of it goes in the description, which the agent reads whole, last line included.
  • Assigned to decides whose task it is; Priority decides what is worked on first when several tasks are waiting.
  • The report under Artifacts goes through your checklist item by item, with the evidence beside each one.

Next​

Next lesson: Task sizing. Previous: Your first task.

Related: