A live, seven-prompt walkthrough your trainers can run in the room. From a fuzzy idea to a scored shortlist to a shareable HTML proposal — every prompt scripted, every expected output shown.
Five minutes of prep, then you can run the whole ideation live. Everything you need is here.
You're a small AI-first startup with three fuzzy ideas competing for the next quarter's engineering focus. The founders have some rough notes, a rough sense of market, and no time to write a formal proposal. Your job in the next 30 minutes — using nothing but Amazon Quick — is to score the three ideas, pick a winner, and produce a shareable one-page HTML brief the leadership team can react to.
Free tier at quick.aws.com is enough for this demo. Enterprise/AWS Console account works too.
Have the fuzzy pitch ready in a note. See the scenario above for the built-in example we'll use in the walkthrough.
Open Quick chat with a clean session. Do not use a Space for this demo — we're teaching prompting, not RAG.
The room must see your prompt window and the AI output side-by-side. Set the browser zoom to 125% before you start.
Tab 4 in this page. You'll hand it out at the end so trainees can rerun the flow with their own ideas.
Don't over-explain. Trainees learn faster watching you fumble a prompt and fix it than by hearing theory upfront.
Run the whole seven-prompt sequence solo the day before, on the exact machine and browser you'll present with. You'll catch Wi-Fi lag, model latency quirks, and the one prompt that produces surprising output. Then jump straight to Tab 2.
Step through the exact prompts to paste into Quick, what each returns, and why we prompt in this order. Click a number below to jump; use ◂ / ▸ to walk in sequence.
Notice the arc: frame → score → drill → challenge → pick → HTML. Every step adds one dimension. Trainees who get this arc can reuse it for anything — hiring calls, feature prioritisation, vendor selection. Teach the pattern louder than the prompts.
What lands after Prompt 7. Quick returns a self-contained HTML file — trainees can download, share, or paste into an email. This is the "wow" moment; make sure everyone sees it.
HTML is the most portable rich format on the planet. It renders in every browser, every email client (Gmail, Outlook), and every doc tool. When you ask Quick for an HTML brief, you get styled headings, tables, cards — no fussing with slide software, no losing formatting in a copy-paste. It also travels better than a link to a Google Doc that half the room can't open.
The exact prompt (see Step 7 in Tab 2) instructs Quick to build a single-file HTML brief with inline styling — one file to send, everything included.
Across the three candidate ideas, Grounded Compliance Copilot ranks highest on a weighted score of market pull, feasibility with our current team, and 12-month cost-to-launch. We recommend focusing the next quarter's build on it, with a 2-week discovery spike first.
| Dimension | Why it wins |
|---|---|
| Market pull | Compliance teams already ask for "AI for policy Q&A" — three inbound requests this month alone. |
| Feasibility | Reuses our existing RAG stack; no new model training required. |
| Cost-to-launch | Estimated 8-week MVP; two engineers plus one design partner. |
This week: 30-min interview with three prospective design partners · Confirm data-handling requirements with legal · Draft a 1-page pilot agreement.
After Quick generates the HTML, hit "Download" in the chat to save a .html file. It opens in any browser, prints cleanly to PDF, and pastes into Gmail as rich content. This is the artefact your trainees will forward to their team the same day.
Hand this to your trainees at the end of the session. Fill in the four bracketed slots, paste into Quick, and the whole ideation runs in one shot instead of seven prompts.
The seven-step flow is for learning — every step teaches a prompting habit (add constraints, ask for scoring, challenge assumptions, request format). The meta-prompt is for doing — once you know the pattern, you don't need to walk through it every time.
Teach the seven steps in the room. Send the meta-prompt in the follow-up email. That way trainees can rerun the flow next Monday with their own three ideas.
| Slot | What to write | Example |
|---|---|---|
| COMPANY NAME | Your one-sentence identity | "PINd.AI, an AI-first fintech tooling startup" |
| Constraints | Team + money + time boundaries | "5 engineers · $200k budget · Q1 launch" |
| Decision maker | Who reads the brief | "Two co-founders + one investor advisor" |
| Ideas 1–3 | One-line pitches | "An AI compliance copilot grounded in our customer's policy library" |
Point out the four constraint types baked into the meta-prompt: context, inputs, task, rules. That structure is transferable — it works for pricing analysis, hiring shortlists, feature prioritisation, vendor selection. The template is more valuable than the specific words in it.
Timing, cues, transitions. Follow the row-by-row playbook — it keeps you honest on the clock and gives you exact things to say.
Quick chat open at 125% browser zoom · this page open on a second tab, ready to switch to the HTML preview · scenario notes on paper next to you · timer visible.
| Symptom | What to do live |
|---|---|
| Quick is slow — the response is taking 30+ seconds | Narrate. "Notice it's still thinking — this is Research doing its work, not a bug." Talk through what you'd expect to see. Never fill silence with apology. |
| Output is generic / low-quality | Perfect teaching moment. Ask the room: "What extra constraint would make this better?" Take a suggestion, add it to the prompt, rerun. Trainees learn faster from a fix than a first-time-perfect demo. |
| Quick refuses (Guardrails or content policy) | Also a teaching moment. "See — Guardrails do their job. Let me rephrase." Rephrase to remove the trigger and continue. Don't dwell. |
| HTML output is broken | Say "the AI got the wireframe right, the styling didn't render — let me ask it to fix that inline". One follow-up prompt: "regenerate with all styles inline and no external CSS references." |
| Wi-Fi drops mid-demo | Switch to this page's HTML preview (Tab 3) and walk the room through the shape while you reconnect. The preview is your backup. |
Trainees will forget most of the specific prompts by next week. What they'll remember is the arc: frame the decision, score with a rubric, challenge the AI's confidence, ask for a shareable format. Repeat that arc in your closing sentence. Everything else is scaffolding.