A guided build we complete together. Give an agent one document, make it answer only from that document, and turn the answer into a briefing.
60 minutes · guided build · no codingYou will build an agent that reads one internal guideline and answers only from it. Click a stop to see what it is.
You are done when you can show all five (tick as you go)
Why a leave guideline. It is not an HR exercise. It is the one internal document everyone has had to interpret, so nobody has to learn the subject, and everybody can judge the answer. The document is neutral ground; the skill is what transfers. Swap in a tender schedule, an SLA annex, an MOH circular or a demand prioritisation framework and the technique is identical. You do exactly that in F4.
Where your F2 prompt gets used. In F2 you filled the five CRAFT slots: Context, Role, Action, Format, Trust. C becomes the Space (Step 1). R and T become the agent you brief (Step 2). A and F become the briefing (Step 4). Keep your Exercise 5 prompt open: you can paste it in place of ours at Step 2 if you would rather build with your own.
One shared build. One synthetic guideline and one set of instructions let a room of 50 keep pace. The deeper build, with full verification and guardrails, is the optional Use Case Deep Dive.
Download the guideline (.md) Read it on this page
You are creating a Space and putting the guideline in it, so the agent has somewhere to look.
What you should see
Do this
Staff Leave Guideline — F3Copy this
Then add the document
f3-guideline-leave.md (from Before you start, or your facilitator’s copy).A Space description is optional metadata. It is not a system prompt and does not steer how any agent answers. Amazon Quick gives you exactly three ways to shape an agent’s behaviour: persona instructions, reference documents, and the Space it can search. The Space is the knowledge layer: it decides what the agent may read, not how it must behave. AWS: chat agent context sources and best practices.
Click Open chat (top-right of the Space page). Click + in the chat box and switch Web search off, then ask: “Using only the leave guideline in this Space, what is its effective date and who owns it? Answer directly.” If it answers 1 April 2026 and People & Culture (HR), it is reading the document itself. Neither fact appears in the Space description, so the description can’t give the answer away.
You describe the agent in plain English, Generate fills in the configuration, and Launch saves it.
What you should see
Do this
Copy this
The brief’s headings are deliberately the shape of Amazon Quick’s own configuration fields, because that is what Generate fills in. CRAFT is how you decide what to write; the Quick fields are where it lands.
| Slot | In the brief | Where it ends up in Quick |
|---|---|---|
| C Context | ## Knowledge source |
The Space from Step 1, attached as the knowledge source. The documents themselves are the context; you don’t paste them. |
| R Role | ## Persona |
Persona instructions. Careful, plain-speaking, never guesses. |
| A Action | ## Goal & Instructions |
Instructions. Answer from the Space, name the section, keep it actionable. |
| F Format | one line inside ## Goal & Instructions |
Thin on purpose: “short, plain language”. A chat agent answers many shapes of question, so the real formatting is specified per request, in Step 4. |
| T Trust | ## Rules |
Instructions, and ideally also a Reference document. |
Optional: add the guideline as a Reference document. Knowledge sources give the agent facts to reason over. Reference documents give it rules to follow, with the wording preserved exactly rather than paraphrased. For a policy agent that must quote entitlements precisely, that matters. On the Configure page, find Reference documents → Upload Files and add the same guideline. Limit: 10 files, 50MB total.
Ask two questions: one the guideline answers and one it doesn’t. A trustworthy agent cites the first and admits the gap on the second.
What you should see
18 days this leave year. Section 3.1
Up to 7 unused days carry forward, used by 31 March. Section 6.1 Section 6.2
This is not covered in the guideline.
Please contact People & Culture (HR), or your Head of Department for exceptions. Section 8
Do this
Ask “Can I cash out 5 unused annual leave days this year?” A good agent answers no, only on cessation of employment and cites Section 6.3.
Ask the agent, in the same chat, for a one-page document you can download and send.
What you should see
Do this
Copy this
Notice what is absent. That is the interesting part.
| C | Not written. The agent already holds the Space. You never re-state the source once an agent is grounded: that is the whole return on Step 1. |
| R | Not written. The persona was set in Step 2 and persists across every turn. |
| A | “create a one-page staff briefing titled … as a Word document I can download”: a named artefact, not an activity. |
| F | The Structure it as: list, the section order, “under one page”. This slot does most of the work here. |
| T | “Using only the guideline” and “Cite the section beside each point”: restated even though the agent already has these rules, because a document that leaves the room needs its citations on the page. |
The lesson to take to F4. Once you have built the agent, your day-to-day prompts get shorter. C and R live in the agent; each request only needs A and F, with T reinforced whenever someone who wasn’t in the conversation will read the output.
Going further. Comment on a specific section in the preview panel and regenerate, and the feedback is applied to just that part. Keep chat for changes across the whole document. You can also upload an existing .docx and ask for edits: Quick keeps the original fonts, styles, headers and footers, which is how you pour this briefing into a house template. A PDF cannot be edited in place, so Quick extracts the content and builds a new one. AWS user guide: document and visual creation in Amazon Quick →
You built a working agent in four moves. Four things made it trustworthy. Click each one.
Not the open internet. Swap the file in the Space and the same agent becomes a different assistant. The pattern travels.
Go to the Agent Design Canvas (F4)
F2 gave you five slots. You have just put each one somewhere real. Swap the document for a tender schedule or an MOH circular and the destination of every slot stays identical.
| Slot | Where it lived in this build |
|---|---|
| C Context | The Space (Step 1). The document itself, not a description of it. |
| R Role | The agent’s persona (Step 2). Written once, applies to every conversation. |
| A Action | Agent instructions for routine answers (Step 2); the briefing request when you want a specific artefact (Step 4). |
| F Format | Mostly per request (Step 4). A general-purpose agent should not over-specify shape up front. |
| T Trust | Agent rules (Step 2), then proven by the two questions in Step 3. |
The document you add in Step 1, and what to do if your laptop blocks file uploads.
Every figure and rule is invented for training. The section numbers are what the agent should cite.
Download f3-guideline-leave.md
Have Amazon Quick create the guideline as a document, then add it straight to your Space. The result is identical to uploading it.
It asks for Markdown, the same format as the .md download, so whichever route you take your Space holds the same document and the tables in sections 3.1 and 5.2 survive exactly as written.
Hidden from participants by default. Press Shift + N to hide it again.
F3 is a 60-minute block. The first 10–12 minutes are a live instructor demo of Amazon Quick; the rest is this shared build. Keep everyone on the same step — this is a warm-up, not a race.
| Block | Facilitator focus |
|---|---|
| 12–22 | Everyone creates a Space and adds the guideline. Read the Space description aloud, then say what it is not — it is a label, not a system prompt. The rules arrive in Step 2, on the agent. Correcting this early stops people expecting the Space to police the answers. |
| 22–34 | Paste the brief, Generate, review the Configure page. Flag the Update preview vs Launch trap early — people lose agents here. |
| 34–46 | Question 1. Check the room has Web Search off first. Circulate. Get everyone to a cited answer before moving on. |
| 46–52 | Question 2. This is the payoff — pause here and discuss what a general chatbot would have done. |
| 52–57 | Step 4 briefing. If short on time, demo it from the front rather than dropping it. |
| 57–60 | Debrief. |
Say it in the first minute: "this is not an HR exercise." A leave guideline is the one internal document everyone in the room has already had to interpret, so nobody spends the hour learning the subject matter instead of the technique — and everyone can judge the agent's answer for themselves. Then name the swap explicitly: "in F4 you point exactly this at a tender schedule, an SLA annex, an MOH circular or a demand prioritisation framework." Rooms that are heavily technical or delivery-focused will otherwise quietly file this module under “not mine”.
If the clock slips, cut Step 4 to a live demo — but never skip Question 2. The contrast between a cited answer and an honest "not covered" is the single learning outcome that carries into every track.
| If you see… | Do this |
|---|---|
| Agent answers Q1 with no citation | Ask it "which section says that?" live. Reinforce that an answer you can't trace is an answer you can't trust. |
| Agent invents a sabbatical policy for Q2 | Celebrate it as the teaching moment. Show the "not covered" rule in the agent's instructions; have them re-ask in a new conversation. Grounding is something you instruct, not magic. |
| Agent gives a wrong number (e.g. 21 not 18) | Usually the file didn't finish indexing, or the agent isn't pointed at the right Space. Check the Space shows the guideline as ready, and that the instructions are intact. |
| Someone says their Space is not in the list | A Space created a moment ago can be missing from the picker until the browser tab is reloaded. Ask them to reload before assuming the step failed. |
| Someone asks about their real leave | Redirect gently — this is synthetic data for learning the pattern, not an HR service. |