Ambitious Model Use - Altitude, Depth and Range

Workflow

1. Create a task per step below, each with its completion criterion.
2. Diagnose the request on each dimension:
   • Altitude: deliverable, or the outcome behind it? Strongest when the work ends in a meeting or decision; weak for open creative work.
   • Depth: raw data and the instruments a field-leading expert uses, or digested summaries? Fits any task the user wants done really well.
   • Range: only the field the task names on its surface? Strongest for creative work.
3. Pick the dimensions with the largest gap and write the rewritten brief using the techniques below. Read references/examples.md first for worked QBR, churn and homepage rewrites.
4. List the access the brief needs (a computer, installable tools, raw data via files or MCP connectors) and flag what is missing.
5. Name the outside judge: a tool, metric or held-out dataset the model runs. The model's own judgement does not count.
6. Present steps 2-5 to the user. Execute the brief only after the user confirms it, applying the Depth and Range techniques yourself.

Altitude Techniques

• Ask the user "what do you want to happen next?" instead of assuming the goal. Only the user can answer it.
• Move from "fix crashes" to "keep the app crash-free". Durable outcomes need workflow changes first: crash-report access, a version-to-commit map, and machines to reproduce and verify fixes.
• Decompose open-ended goals ("go make money") into outcomes the model can verify.