# The /goal Framework: Learning Game Edition

> Framework credit: this is **Sabrina Romanov's /goal prompt structure**, five
> labeled blocks that turn a vague idea into a buildable brief. The original slide
> (`dragon_goal.png`) used it to build a dragon *game*. This version refits the
> same five slots to build a dragon *learning game*, a quiz your learners fly
> through.

## The five slots

| Slot | What it does |
|------|--------------|
| **TASK** | The one thing you want built |
| **WHY** | The reason it matters. This shapes every tradeoff Claude makes |
| **OUTCOME** | What "done" looks like, concretely |
| **CONSTRAINTS** | The fences: what to use, what NOT to touch, hard limits |
| **VERIFICATION** | Observable behaviors, the things *you can do* when it works |

The magic is in the last two. CONSTRAINTS keeps Claude from wandering.
VERIFICATION is written as things a human can observe, so "done" is not a vibe,
it is a checklist.

## Original (game) vs. Learning Game Edition

**Original, from `dragon_goal.png`:**

```
/goal
TASK: Build a game where I can pilot a dragon through a fantasy world.
WHY: Make flying feel thrilling, strong, and easy to learn.
OUTCOME: A playable game with flying, landing, fire breathing, and simple goals.
CONSTRAINTS: Simple controls, POV from on top of the dragon, Elden Ring themed.
VERIFICATION: I can start, fly, complete a goal, and play without major bugs.
```

**Learning Game Edition, what we're building today:**

```
/goal
TASK: Turn my four training questions into a playable dragon-flight quiz game.
WHY: Learners remember what they DO. A decision made mid-flight sticks better
     than a click on "Next."
OUTCOME: A shareable web game: 3 question gates to fly through, 1 fire-breathing
     question, a landing finale, and a score my LMS can read.
CONSTRAINTS: Use the skyvale-quiz-flight engine as-is (never rewrite the flight
     physics). 3 gate questions with 2 to 4 answers, 1 fire question with exactly
     3 answers, every answer under 6 words. Passing score 300.
VERIFICATION: I can fly through all 3 gates, tap F once to answer the fire
     question, land on the beacon, and see a score, with MY questions on
     screen, not the samples.
```

Notice what changed and what did not. The five slots are identical. Only the
*content* moved, from "build me a toy" to "build me a teaching tool." That is the
whole workshop in one slide: the framework is reusable; you swap the brief.

## Blank template, fill in yours

```
/goal
TASK: Turn my four training questions about ______________ into a playable
      dragon-flight quiz game.
WHY: ______________ (what should your learners feel or remember?)
OUTCOME: A shareable web game: 3 question gates, 1 fire question, a landing
      finale, and a score my LMS can read.
CONSTRAINTS: Use the skyvale-quiz-flight engine as-is. 3 gate questions (2 to 4
      answers each), 1 fire question (exactly 3 answers), answers under 6 words.
      Passing score ______.
VERIFICATION: I can fly all 3 gates, tap F once for the fire question, land on
      the beacon, and see a score, with MY questions on screen.
```

Tip: TASK, OUTCOME, and CONSTRAINTS can stay almost verbatim. Your voice lives in
WHY. That is the slot that makes it *your* learning game.