The outcome

Use Roo's specialized modes without giving an agent broader access or autonomy than the task requires.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch, capture the baseline status and tests, and inspect repository rules, architecture, secrets, and generated-file boundaries.

  2. 02

    Choose Ask or Architect mode first and provide the outcome, acceptance criteria, relevant paths, non-goals, and exact validation commands.

  3. 03

    Review Roo's explanation and minimal plan, then switch deliberately to Code mode with auto-approval disabled or narrowly allowlisted.

  4. 04

    Approve only understood tool calls, inspect edits and terminal commands as they occur, and reject browser, MCP, dependency, or scope expansion without justification.

  5. 05

    Run trusted checks independently, inspect the complete diff and cost, and submit through normal peer review without granting Roo release authority.

Working standard

What good use looks like.

  • Plan before Code mode.
  • Keep command auto-approval narrow.
  • Verify the final diff independently.

Official references

Check the current product documentation.