promptdojo_

Turn old deliverables into interactive site artifacts — step 2 of 3

Checkpoint

One last thing before we move on. Same surface as a write step — but the lesson doesn't complete until this passes.

Build-brief checkpoint. You just saw a finished brief for the Q3 roadmap presentation. Now transform a different deliverable yourself.

The scenario. Every Monday morning someone on your team pastes ticket counts into a long weekly support metrics email. The people who actually read it are the support team leads planning staffing for the week. What they really need to decide is which queue gets the extra agent this week. The raw material already exists: the ticket export, last week's email, and the on-call notes. A small site could show queue volumes, response times, and a week-over-week chart — and let a lead filter by queue. Two catches: ticket data lags by a day, and customer names can't appear on a shared page. You'd call it done when a lead can pick the queue for the extra agent in under five minutes. It could live at /internal/support-staffing.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, "Show example" reveals a model answer.

full-screen editor opens — close anytime to keep reading.