Your first outcome in 60 seconds
Open Claude Code, ask for an outcome, watch DOS pick a mode and deliver. No Packs to choose, no commands to memorize.
cd into any git repo, run claude, and paste this:
That's the whole first move. No Pack picked, no Skill named, no slash command — just the outcome you want to be true. DOS reads the request, classifies it, picks a mode, and runs.
What lands on your screen
DOS will reach for ALGORITHM mode (multi-step: read git log, rank files, synthesize). The response opens with a header that looks like this:
The mode header is the tell. DOS announced which gear it shifted into before it did the work.
The three modes
NATIVE — quick single-step tasks. Lookups, renames, one-file edits. ALGORITHM — multi-step work. Investigation, planning, refactoring, anything that needs phases. MINIMAL — greetings, ratings, acknowledgments. No ceremony.
Same sentence you'd brief a sharp coworker with is the sentence that drives DOS. Quick asks finish in seconds. Research asks spin up a sprint. No tool-switching on your end.
Try these next
Brief me on what this codebase does in 5 bullets.
Find the riskiest file in this repo and tell me why.
Draft a one-pager for stakeholders about what this service does.
Look at the last 10 commits and tell me who's working on what.
Each one picks its own mode. Watch the headers — they tell you what DOS decided the request needed.
Next
Read How to ask DOS for things for the mental model behind outcome-shaped requests.
Was this page helpful?