← →

Day 28: Capstone Part 1, Build the Source and Strategy Foundation

Cue’s invitation · Day 28 of 30

One small win today

Name one reader, two small deliverables, and a fact you must not overstate.

Let’s try it One prompt is enough. Rough drafts welcome.
CueFolioYour narratorPrism

Listen with Folio

Folio guides you through the whole lesson. Listen straight through, or choose a chapter. Pause whenever you want to try something.

Complete podcast · 9 min 18 sec · AI-generated character voice

Jump to a chapter

Day 28: Capstone Part 1, Build the Source and Strategy Foundation audio transcript

Welcome

Folio: Hi, I’m Folio. Welcome to the Day 28 lesson: Capstone Part 1, Build the Source and Strategy Foundation. I’ll guide you through the whole lesson. Pause whenever you want to try something. Chapter links and the full transcript are available alongside the player, so you can return to the part you need.

Your one useful idea

Folio: Cue says: Which two useful results could make a small workplace package? Prism says: Keep the sources, limits, and review notes beside them. Start with what you can explain. Combine a few useful results into one small package. Here’s the one idea to keep in your pocket today. Choose one reader and two small deliverables that fit three short sessions. Sample sources and one approved assistant are enough.

Why this helps

Folio: Let’s connect this to a real working day. Cue says: Your capstone can be small. Choose one task worth doing, gather the facts, and agree with yourself what a useful finished package will contain.

Before you begin

Folio: A quick check before we get our draft-making shoes on. Keep the scope within the next three short sessions. You can use the course samples throughout, and one approved assistant is enough.

Try it together

Folio: Ready to make a little progress? Here’s the quick route and the full practice. You can pause after the steps and work in your own time. Quick version: Name the reader and two deliverables, then list the one fact you must not overstate. About 10 minutes is enough. Step 1. Choose a task such as a support-guide pilot or a weekly team update. Step 2. Gather two or three safe inputs and name the reader. Step 3. Write the deliverables, unknowns, and review boundary in a short brief. Practice material or example: Mock capstone: support-form pilot. Inputs: pilot plan, review note, feedback note from Days 14 and 15. Outputs: a 150-word team update and a single-sheet review checklist. No publication is included.

Simple and Expanded prompts

Folio: Time to frame the request. Both prompt versions are in this lesson. You only need to try one. I’ll read both versions so you can hear the difference. Pause and copy the exact text from the lesson if you’re practising. Here’s the Simple prompt. Create a capstone brief from these mock inputs: Source A, Pilot plan: Five internal volunteers will test the request form Monday. Feedback is due Thursday. Source B, Review note: Response times have not been measured. No customer rollout is approved. Source C, Preview feedback: Three volunteers requested clearer labels during a preview. Include reader, goal, two small deliverables, source list, unknowns, and human review needed. Keep it under 180 words. Plan only, with no external actions. Here’s the complete Expanded prompt. Create a capstone brief from these mock inputs: Source A, Pilot plan: Five internal volunteers will test the request form Monday. Feedback is due Thursday. Source B, Review note: Response times have not been measured. No customer rollout is approved. Source C, Preview feedback: Three volunteers requested clearer labels during a preview. Include reader, goal, two small deliverables, source list, unknowns, and human review needed. Keep it under 180 words. Plan only, with no external actions. Name the internal support team as reader. Specify only a 150-word update and a single-sheet review checklist. Map facts to Sources A–C. Exclude publication, customer rollout, and claims about speed. Keep this brief small enough for the next two sessions. Pick the version that fits your task. One useful prompt is enough. Give it a try when you’re ready.

A worked example

Folio: Let’s open a little window onto one possible result. This example is written for the course. Your assistant’s answer can look different. One possible result: Goal: help the internal team prepare a pilot review. Deliverables: one short update and one review checklist. Review boundary: check source claims and get support-lead approval before any real use. Why it works: The brief is small enough to finish and makes its evidence and limits explicit. Cue says: Choose one reader and two small things worth making. A short update and a review checklist are enough. Keep the sources and unknowns beside them. Watch for: A proposal for a slide deck, website, campaign, and dashboard would turn a small capstone into a new project.

Spot the Wobble

Folio: Tiny detective break! Let’s spot the wobble. Draft to check: Capstone: a website, slide deck, campaign, and dashboard. Question: What makes a manageable capstone for this course? A: One reader, two small deliverables, and a clear review boundary. B: As many outputs as the assistant can generate. What do you think?

*A short thinking pause. Pause the player for as long as you need.*

Folio: Here’s Prism’s check. The answer is A Why: A small capstone lets you practise checking and consistency. Choose a short update and review checklist rather than a new project. A wobble is a clue, not a disaster. That little check is how a draft gets stronger.

Keep something useful

Folio: Let’s give your useful work a home. Save capstone brief with one reader and two small deliverables for the full practice, or just keep your checked quick result. Keep the input beside it and note one thing you checked.

Review and save

Folio: Time for the satisfying bit: checking what you made. The quick finish counts. You don’t have to do every extra. Are the deliverables small enough, and can each important fact be traced to an input? Quick finish: Name one reader, two small deliverables, and a fact you must not overstate. You can stop here. Done when: Full practice: Your brief names one reader, two small deliverables, source inputs, unknowns, and the human review boundary. You can stop here. Extra practice, only if useful: Define one simple way to tell whether the package helped its reader.

Your optional official video

Folio: If you’d like to see the tool in action, there’s an optional official video embedded in this lesson. We’ll explain what to notice. You can watch later. Notice the kinds of artifacts a team can make and the human judgment needed before shipping. Which two small deliverables belong in your capstone? Watch: Use ChatGPT Work to turn marketing ideas into finished work (official OpenAI YouTube channel, published September 4, 2026, verified October 2, 2026). Keep it small: Watch from 1 minute and 38 seconds to 2 minutes and 29 seconds, about 51 seconds. The business workflow is larger than today’s task. Keep your capstone to two reviewable outputs with an explicit stopping point. Watching is optional.

Questions you might be wondering

Folio: Two questions you might be wondering about. Let’s clear them up. How large should my AI course capstone be? Choose one reader and two small deliverables that fit three short sessions. Sample sources and one approved assistant are enough. What should I settle before drafting the capstone? Name the goal, safe sources, unknowns, deliverables, and human review boundary in a short brief.

Quick quiz: question 1

Folio: Question 1 of our three little checks. Which capstone scope fits today's approach? Option A. Launch a new platform and train the whole organization. Option B. Connect every available assistant to every source. Option C. Create a 150-word team update and a single-sheet review checklist for one reader. Want a hint? Aim for two small deliverables across three short sessions. Pause to choose. Keep listening when you’re ready for the answer.

*A short thinking pause. Pause the player for as long as you need.*

Folio: The answer is C. Create a 150-word team update and a single-sheet review checklist for one reader. A narrow scope makes the project realistic and gives you time to check it.

Folio: If you spotted it, lovely work! If you picked another answer, you’ve found something useful to practise. There’s no score to chase.

Quick quiz: question 2

Folio: Question 2 of our three little checks. What belongs in the capstone brief? Option A. Only a catchy project name. Option B. Reader, deliverables, safe sources, unknowns, and the review boundary. Option C. A promise that every proposed result will happen. Want a hint? The brief should guide both drafting and checking. Pause to choose. Keep listening when you’re ready for the answer.

*A short thinking pause. Pause the player for as long as you need.*

Folio: The answer is B. Reader, deliverables, safe sources, unknowns, and the review boundary. These details connect the work to its audience, evidence, and permitted actions. Another little check in your toolkit. You’re building a habit one answer at a time.

Quick quiz: question 3

Folio: Question 3 of our three little checks. What external action is included in the mock capstone? Option A. None. Publication requires a separate approved action. Option B. Automatic customer rollout. Option C. Sending the draft to every colleague. Want a hint? Today's brief authorizes draft outputs, not distribution. Pause to choose. Keep listening when you’re ready for the answer.

*A short thinking pause. Pause the player for as long as you need.*

Folio: The answer is A. None. Publication requires a separate approved action. The mock capstone explicitly excludes publication, leaving that decision with a person. Three checks, one stronger understanding. The online quiz lets you try again until each answer clicks.

Your next small step

Folio: Before you leave, keep the original input beside your checked result. Your judgment is the part no assistant can replace. You made room for one useful step today. That counts. Day 29 is ready whenever you are. Cue asks, Folio makes, Prism checks. See you for your next small win!

The cast plans two small capstone artifacts and a final review.
The cast plans two small capstone artifacts and a final review.

Combine a few useful results into one small package.

See today’s example with your practice partners
Cue scopes two small capstone artifacts while the cast keeps sources and review visible.
Cue scopes two small capstone artifacts while the cast keeps sources and review visible.

Key Takeaway

Choose one reader and two small deliverables that fit three short sessions. Sample sources and one approved assistant are enough.

Why It Matters

Cue: Your capstone can be small. Choose one task worth doing, gather the facts, and agree with yourself what a useful finished package will contain.

Know Before You Try

Keep the scope within the next three short sessions. You can use the course samples throughout, and one approved assistant is enough.

Make with Folio

Try It

Quick version: Name the reader and two deliverables, then list the one fact you must not overstate. About 10 minutes is enough.

  1. Choose a task such as a support-guide pilot or a weekly team update.
  2. Gather two or three safe inputs and name the reader.
  3. Write the deliverables, unknowns, and review boundary in a short brief.

Practice material or example: Mock capstone: support-form pilot. Inputs: pilot plan, review note, feedback note from Days 14 and 15. Outputs: a 150-word team update and a one-page review checklist. No publication is included.

Ask with Cue

Prompt

Primary Prompt

Pick one to try. Simple gets you moving. Expanded adds structure. Both include the practice inputs.

Simple Prompt

Create a capstone brief from these mock inputs:
Source A, Pilot plan: Five internal volunteers will test the request form Monday. Feedback is due Thursday.
Source B, Review note: Response times have not been measured. No customer rollout is approved.
Source C, Preview feedback: Three volunteers requested clearer labels during a preview. Include reader, goal, two small deliverables, source list, unknowns, and human review needed. Keep it under 180 words. Plan only, with no external actions.

Expanded Prompt

Create a capstone brief from these mock inputs:
Source A, Pilot plan: Five internal volunteers will test the request form Monday. Feedback is due Thursday.
Source B, Review note: Response times have not been measured. No customer rollout is approved.
Source C, Preview feedback: Three volunteers requested clearer labels during a preview. Include reader, goal, two small deliverables, source list, unknowns, and human review needed. Keep it under 180 words. Plan only, with no external actions.

Name the internal support team as reader. Specify only a 150-word update and a one-page review checklist. Map facts to Sources A–C. Exclude publication, customer rollout, and claims about speed. Keep this brief small enough for the next two sessions.

Worked Example

: see a result and what to check

One possible result: Goal: help the internal team prepare a pilot review. Deliverables: one short update and one review checklist. Review boundary: check source claims and get support-lead approval before any real use.

Why it works: The brief is small enough to finish and makes its evidence and limits explicit.

Watch for: A proposal for a slide deck, website, campaign, and dashboard would turn a small capstone into a new project.

Prism’s optional 30-second puzzle

Spot the Wobble

Draft to check: Capstone: a website, slide deck, campaign, and dashboard.

What makes a manageable capstone for this course?

  • A. One reader, two small deliverables, and a clear review boundary.
  • B. As many outputs as the assistant can generate.
Reveal Prism’s check

A is the better choice. A small capstone lets you practise checking and consistency. Choose a short update and review checklist rather than a new project.

Spotted it? Nice checking. Missed it? Now you know what to look for.

Make Something Useful

Save capstone brief with one reader and two small deliverables for the full practice, or just keep your checked quick result. Keep the input beside it and note one thing you checked.

Check with Prism

Review and Save

Are the deliverables small enough, and can each important fact be traced to an input?

Quick finish: Name one reader, two small deliverables, and a fact you must not overstate. You can stop here.

Done when: Full practice: Your brief names one reader, two small deliverables, source inputs, unknowns, and the human review boundary. You can stop here.

Want one more little stretch?

Define one simple way to tell whether the package helped its reader.

An optional little watch break

Watch with Folio

Folio: Notice the kinds of artifacts a team can make and the human judgment needed before shipping. Which two small deliverables belong in your capstone?

Watch: Use ChatGPT Work to turn marketing ideas into finished work (official OpenAI YouTube channel, published September 4, 2026, verified October 2, 2026).

Show video player: Use ChatGPT Work to turn marketing ideas into finished work

Prefer another way to watch? Open this video on YouTube (new tab). Use captions or YouTube’s transcript when available. The lesson text covers the skill too.

Keep it small: Watch from 1:38 to 2:29, about 51 seconds. The business workflow is larger than today’s task. Keep your capstone to two reviewable outputs with an explicit stopping point. Watching is optional.

FAQ

How large should my AI course capstone be?

Choose one reader and two small deliverables that fit three short sessions. Sample sources and one approved assistant are enough.

What should I settle before drafting the capstone?

Name the goal, safe sources, unknowns, deliverables, and human review boundary in a short brief.

Prism’s optional quick quiz

Three little checks

“Let’s see what stuck! Pick an answer and I’ll help you check it. You can try again as often as you like.”

Question 1 of 3

Which capstone scope fits today's approach?

No score, no rush. This is optional and does not change your lesson progress.

A small win worth keeping

Checked and saved? You can call it a day. Come back when you’re ready.

Progress is saved in this browser when available.

Stored on this device. No account or cross-device sync.

Course position: Day 28 of 30 · Capstone Project module
Continue: Day 29: Capstone Part 2, Create the Productivity Package

Sources and review date

Product features and interfaces can change. Official learning references is the reference for current details. Course content reviewed October 2, 2026.