Skip to main content
Building on pre.dev has two independent axes, plus a model picker:
  1. Sprint mode — what to build next: the next roadmap task, the whole roadmap on autopilot, or a custom task you describe.
  2. Effort level — how deep each sprint goes: a fast direct pass, a task-list loop, or the full research → code → verify pipeline.
  3. Model picker — which model runs each phase of the work.

​
Sprint mode: what to build

Agents build one roadmap task at a time, then wait for your review before proceeding.
1

Task assigned

The next incomplete task from your roadmap is assigned to the coding agent
2

Agent builds

The agent implements the task in a secure sandbox
3

Verification

Acceptance criteria are verified (types, lint, tests, browser)
4

You review

Review the result, give feedback, then continue to the next task
Best for: learning how pre.dev works, sensitive codebases, and teaching the agent your preferences by reviewing early tasks.

​
Choosing a sprint mode

You can switch modes at any time: validate the first few tasks one at a time, flip to Autopilot once the agent has your patterns down, and drop into chat whenever you need a quick change.

​
Effort level: how deep each sprint goes

Set the effort level with /effort: When each is right:
  • Vibe (low) — UI tweaks, copy changes, small features where speed matters more than process.
  • Todo (medium) — multi-step features that benefit from a visible task list but don’t need a research phase.
  • Build (high) — complex features, integrations, and anything where you want the agent to research the codebase first and verify acceptance criteria at the end.
  • Auto — let pre.dev pick per sprint. Good default if you don’t want to think about it.
Effort applies per sprint: the setting at launch time governs how deep that sprint goes. Higher effort uses more credits — the research and verification phases are extra model work.

​
Model picker: which models do the work

Every sprint moves through phases, and you can pin a different model to each with /model: Available models: Typing /model walks you through it: pick a phase, then pick a model. Set a phase back to Default to return it to GLM 5.2.

​
Pro Mode

/pro is the one-toggle shortcut: it pins every phase to the Pro model (Claude Opus 4.8) for maximum quality. Pro Mode uses more credits per sprint, so a common pattern is to iterate in standard mode and flip on Pro for final production passes. See Pro Mode & Model Selection for details, and pricing for plan differences.

​
What’s next?

Verification

How every task is verified before it counts as done.

Roadmap & Tracking

Watch build progress in real time from the roadmap.