The outcome

Finish a scoped coding task with a clear plan, reviewable diffs, and evidence that the change works.

Step by step

A workflow you can repeat.

  1. 01

    Start on a clean branch, describe the expected behavior and constraints, and point Cline to the relevant files and project instructions.

  2. 02

    Use Plan mode to inspect the repository, identify affected code and tests, surface assumptions, and agree on a bounded implementation plan.

  3. 03

    Confirm Checkpoints are enabled, switch to Act mode, and approve file edits and commands individually unless a narrow action is already trusted.

  4. 04

    Review each diff and terminal result, redirect Cline when scope expands, and restore the last good checkpoint if the approach goes wrong.

  5. 05

    Run the project checks, inspect the final diff and git status yourself, then commit only after the acceptance criteria are demonstrated.

Working standard

What good use looks like.

  • Plan before medium or large changes.
  • Keep destructive actions approval-gated.
  • Treat tests and the final diff as the completion evidence.

Official references

Check the current product documentation.