Skip to main content

Staying in the loop

Lesson 4 of 10 · 5 min 31 s. Start a task Guided and answer the agent when it stops to ask, find every answer in Q&A, and see how a change that touches sign-in is reviewed before it ships.

Before you start​

  • You have done Task sizing and are signed in to the console.
  • You have a project you can start tasks in, with tests the agent can check its work against. The lesson uses TimeSaver, a time-tracking app for small teams.

Steps​

  1. Open the new-task form in your project and describe the work, including which decision stays yours. The lesson's description is: Let people archive a project they no longer use, so it stops showing in the project picker. Check with me before deciding what happens to its entries. That last sentence tells the agent which decision belongs to you, so it stops and asks before it makes it.
  2. Under the description, look at the second choice, how involved you want to be. It has three positions: Unattended lets the agent decide everything and come back when it's finished; Guided has it stop and ask you before a decision that matters, then carry on with your answer; Interactive asks like Guided, then has you pick Finish or Request changes once the work is done. Leave Guided chosen, the form's default, and press Go.
  3. Watch the task's line on Tasks. The agent reads the code to see what the change involves, and a few minutes later its mark changes and the task is asking. The work waits for you from here, anyone on the team can see a person is needed, and the agent keeps everything it has worked out so you can answer when it suits you.
  4. Open the task; it opens on its questions. Each question says what the agent needs to decide, and under it are the options it sees, each with a line on what it would mean, and the one it recommends first. To answer, click an option, or write your own answer in the box above them if none is right. Once every question has an answer, the agent picks the work back up where it stopped.
  5. Open Activity, then Q&A. Here is every question the agent asked, the options it offered, and the one you chose, with who chose it and when. It's the record to point to when someone asks, months later, why the change works the way it does.
  6. When the work is finished, open Details. The Outcome says what was built, and it follows the answers you gave: the agent settled the small decisions itself and brought you the one that was yours. The change passed the team's tests like any other and is in production.
  7. Now a change most teams want checked before it ships. Start a new task. The lesson's description is: Add a sign-in screen to TimeSaver: people set a password in Settings, and the app asks for it before it shows their entries. Signing in, passwords and personal data are the kind of change most teams want a person to approve before it reaches production. Choose Unattended and press Go.
  8. When the task is finished, open it, then Details. It ran Unattended, so it didn't stop to ask anyone; before delivering, the agent had the change checked by separate reviews, including one for security. The Outcome says what it built, how the password is stored, and that every review passed.
  9. To approve a change like this yourself, start it Guided instead. The agent then asks you before anything ships.
  10. Try it on TimeSaver's own site. In Settings, set a password, confirm it, and sign out. Then open the timesheet: instead of your entries, the app asks for the password first.

What you learned​

  • Choose Unattended when the work is clear, and Guided when some decisions are yours.
  • A Guided task stops to ask: its mark shows it's asking, you answer by clicking an option or writing your own, and the agent carries on.
  • Every question and answer is kept under Activity, then Q&A, with who answered and when.
  • A change that touches sign-in is reviewed, security included, before it ships on Unattended; start it Guided to approve it yourself.

Next​

Next lesson: Personas and models. Previous: Task sizing.

Related: