Best Practices

Start With The Smallest Useful Mode

Use Sessions first unless you already know you need Kanban policy or Team coordination.

Configure One Working Provider First

Do not front-load every provider, model, and role default. One provider path that can execute real work is enough for a successful start.

Keep Work Workspace-Scoped

Treat the workspace as the main operating boundary. Repositories, sessions, tasks, and automation should stay attached to that workspace instead of relying on implicit global state.

Use Kanban For Repeatable Delivery

If you want clear review boundaries, artifact expectations, and handoff visibility, move the work to Kanban instead of trying to simulate that process in one session.

Use Team Only When Coordination Is Real

Use Team when multiple specialties truly need to work together. Do not default to Team for simple implementation tasks.

Keep Reference Material Out Of The Critical Path

Users should reach their first useful run before they need product specs, design docs, or deep reference material. That is why Getting Started and Use Routa should stay simpler than internal repository documentation.