Free preview5 min

The Challenge Briefing

Reviewed by Human · Updated August 11, 2026

What Does a Complete Prompt Workflow Look Like?

Most people who "know prompting" freeze the moment a task needs more than one prompt. They can write a sharp single instruction — and then panic when a real job has three moving parts that feed each other. That's the whole point of this boss challenge. You won't write one clever prompt. You'll design a system. **Workflow**: A set of prompts that run in sequence, where each prompt's output becomes the next prompt's input. Here's the scenario you're building for. An independent consultant lands a client with a messy business problem. The consultant needs three things, in order: a rigorous analysis, a structured report built from that analysis, and a short executive summary email a busy CEO will actually read. One brain-dump prompt won't get there. A designed chain will.

You've used role prompting and chain-of-thought separately. This is where they stop being tricks and start being architecture.

You already have every skill this needs.

Framework, role, chain-of-thought, few-shot, chaining, constraints, error recovery — you met all seven across Arc 2. Nothing new gets introduced here. The challenge is choosing which skill goes where. That decision is the actual job.

What will the expert solution in Module 5 actually contain? Guess before you look.

Your turn

Before you design anything, sketch the seams. In plain English, write the three stages of this workflow and — for each — name what it receives and what it hands off. Don't write prompts yet. Just map the handoffs.

Reflect

Which handoff felt vaguest? That seam is where your workflow will break first — flag it now.

📚

Go deeper

end of module

You've finished this module.

Mark it complete to earn your XP and keep your streak alive.

Progress saved locally · Sign up to earn XP

Design the System Prompt→