The outcome

Produce a scoped, tested change without letting permissive defaults or autonomous execution bypass review.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch, capture repository status and baseline checks, and inspect project guidance, generated files, and sensitive paths.

  2. 02

    Review global and project permission rules, changing shell, edits, external directories, web access, MCP, skills, and subagents to ask or deny where appropriate.

  3. 03

    Give the planning agent the outcome, acceptance criteria, relevant paths, non-goals, and validation commands, then approve a minimal implementation plan.

  4. 04

    Use the coding agent interactively, reviewing every consequential action, changed file, dependency, command, test result, and attempt to broaden scope.

  5. 05

    Run trusted checks independently, inspect the complete diff and usage cost, and merge or deploy only through the repository's normal human-approved workflow.

Working standard

What good use looks like.

  • Audit defaults before the first prompt.
  • Use interactive mode for consequential work.
  • Keep release actions human-controlled.

Official references

Check the current product documentation.