The outcome

Finish a scoped coding task without confusing repository trust, tool approval, and operating-system isolation.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch or disposable checkout, inspect repository settings and hooks, and capture the starting status and baseline tests.

  2. 02

    Start in plan or default mode, add deny rules for secrets, Git metadata, pushes, deployments, and unrelated paths, then enable a restricted shell sandbox.

  3. 03

    Provide the outcome, acceptance criteria, relevant files, architecture constraints, non-goals, validation commands, and a clear stop condition.

  4. 04

    Review the plan and every consequential tool call, rejecting extra directories, network domains, unsandboxed retries, dependency drift, or parallel tasks without need.

  5. 05

    Run trusted tests independently, inspect artifacts and the complete diff, clean temporary credentials, and use the normal human-reviewed commit and release process.

Working standard

What good use looks like.

  • Use deny rules for hard boundaries.
  • Keep shell work sandboxed.
  • Treat directory trust and tool approval separately.

Official references

Check the current product documentation.