How to ask DOS for things
The mental model: describe outcomes, not Packs. DOS picks the tools. This is the most important page on the site.
Say what you want to be true when the work is done. DOS reads your request, chooses the Packs, and runs them. Everything else on the docs site builds on this one habit.
The shape of a good request
Name Packs and you hand-pick from a subset of what DOS knows. Name an outcome and the Algorithm reads the full skills index, picks an effort tier, and composes the Packs you would have forgotten.
The first request breaks the day Research is renamed. The second works next month, next version, next model.
A real receipt
On March 3, 2026 I asked for "a landing page hero that passes a senior CRO review and sounds like our brand voice." The Algorithm pulled Brand, DreamTeam, and a Splitting Test pass I would have skipped. I never named a Pack. The hero shipped that afternoon.
The kitchen, in three lines
DOS is a stocked kitchen. The Algorithm is the chef. You order the dish — medium rare, potatoes on the side — and let the chef decide which cookbook to open.
The one exception — three identical asks is a Feature Request
The first time you describe an outcome, you're making a request. The second time, it's a coincidence. The third time you phrase the same ask the same way, you've found a workflow — that's the moment to file a Feature Request. The DOS team curates Packs in response to repeated patterns; you don't have to build the Pack yourself.
Stacking Packs is doing the Algorithm's job by hand
"Run Research, then Brand, then DreamTeam" overrides effort-tier selection, parallelization, and the Splitting Test. You'll get a slower, worse answer than if you'd described the end state in one sentence.
Next
Read The Algorithm to see what happens between your outcome and the finished work.
Was this page helpful?