Opens in a new tab
Skip to main content
Lesson 10 of 10

Repeat the Note-to-Draft Routine

Bring a small task, current source, clear draft and review into one reusable everyday flow.

About 10 minutesNo coding experience neededExplore in your browser

Look around. Try a small click.

This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.

Read the short lesson

What will make more sense

  • Repeat a small source-to-draft-and-review routine.
  • Choose a next step based on the document’s actual state.

One idea to keep

Give the assistant a clear task, then review the words and the state.

The short lesson

Read the explanation at your pace

You now have a useful routine for ordinary AI-assisted work. Choose one document, identify the current source, ask for a small draft, compare the result and record its status. That sequence works for more than invitations. You can use it for a meeting summary, a clearer staff instruction, a customer explanation or a checklist that organizes a rough note.

Begin by describing the audience and useful result. Then make the relevant material available deliberately. The Willow Workshop example uses a short fact sheet and a rough note, not an entire business archive. A different task might use an approved product description or a meeting record. The source should match the claim you want the document to make.

Ask for the writing change in ordinary language. You can request two sentences, a calmer tone, a clearer order or a short action list. Add the boundaries that matter, such as preserving confirmed facts and leaving the result as a draft. You do not have to write the final words yourself, but you should be able to say what the result needs to achieve.

Review before moving on. Compare important wording, check names and numbers against their sources and notice any unsupported promise. If one paragraph works and another does not, ask for a narrow revision. The goal is not to keep prompting until the output feels impressive. It is to produce a document that serves its audience and represents the business accurately.

Finish with an honest status and a next step. The draft might be ready for owner review, waiting for a missing date or approved for a specific internal use. Sending, publishing and account connections remain separate tasks. A handover note can preserve that state for the next session, while a suitable history routine can help explain meaningful file changes later.

In the final browser activity, choose the repeatable scoped workflow. Then explore another course if you want a deeper method: Helpful Context explains source selection, Git explains recorded changes and Agent Files shows how supported reusable instructions can capture your preferred process. None requires you to begin as a programmer. You are learning to direct useful work and judge the result with clear business understanding.

Try it here

Try it here · no installation needed

Choose the repeatable routine

Explore the prepared example, then choose a response. Your choice reveals its explanation immediately.

This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.

STEP 1One task and its current source
STEP 2A draft you can compare
STEP 3An honest status and next step

Which sequence keeps everyday AI work understandable?

A tiny next step, if you want one

Optional: try 2 small actions at your own pace

You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.

  1. Optional: read next-task.md and identify its source, output and boundary.
  2. Optional: use the review checklist in review-status.md on the prepared draft.

A quick confidence check

These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.

Your place is saved in this browser when storage is available. There is no grading or account sync.

Try a short question

Choose an answer to see why it fits. You can try again or explore every explanation.

What should guide the next step?

Do you need to write code to use this routine?

If something looks different

You want to automate the sending step next.

Treat that as a separate project with its own connection, audience, permissions and review plan. The drafting course has not configured it.

Keep learning

Keep learning with another focused course. Each has its own written lessons, examples and prepared files.

Organize your work

Helpful Context and Project Memory

Give your assistant the right facts, project notes and handovers without assuming it remembers everything. Learn to select sources, resolve stale information and keep useful context easy to find.

10 written lessons · Guided browser activities · Free to read

Explore this course
Understand your agent

Git and the Story of Your Changes

Understand saved files, recorded checkpoints and useful change notes through visual examples. Review an agent’s edits before preserving a milestone, without typing Git commands.

10 written lessons · Guided browser activities · Free to read

Explore this course
Organize your work

Agent Files and Reusable Skills

Turn your working methods into supported project instructions and small SKILL.md packages that an assistant can use and you can review.

10 written lessons · Guided browser activities · Free to read

Explore this course

Sources and further help

Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.