Workflow Windsurf Cascade Plan et Write : planifier, un diff, git diff

Plan → Write un diff → relecture git diff.

After Windsurf Cascade is installed and signed in, the next failure mode is workflow: staying in Chat for a multi-step refactor, or hitting Accept All on a pile of unread diffs. Use Plan to outline, switch to Write for one reversible change, then review with git diff.

The query is Windsurf Cascade Plan and Write workflow with reviewable diff. This page follows Cascade notes at windsurf.com and docs.devin.ai/windsurf (mode names and shortcuts can change—trust the live UI). First install is in our Windsurf Cascade install guide; stale sessions in refresh after update. Not a meeting-product guide—walk a diff on wbmeet; see create and join a room.

Plan, Write, and Chat in Cascade

Cascade is Windsurf’s repo-level agent. Official docs describe agent modes including planning versus editing; in the product UI you typically pick Plan (or equivalent) to break work into steps without touching files yet, Write to propose file edits and terminal commands, and Chat for read-only Q&A. Hour two is about picking the right mode—not repeating installer steps.

Plan mode: scope before Write

1. 1

   Open Cascade at the repo root

   Cmd+L / Ctrl+L or the Cascade sidebar. Run git status in the integrated terminal first so you know what is already dirty.

2. 2

   Select Plan (or planning mode)

   In the mode picker, choose Plan when the task spans more than one file—refactors, new feature skeletons, test coverage gaps. Ask: “List 3–5 steps to add input validation to parseUserId only; do not edit files yet.”

3. 3

   Narrow with @ context

   Use @ to attach one file or folder (official Cascade context UI). Reject plans that rename half the repo; reply: “Scope to one file and one test file only.”

Write mode: one reviewable diff

1. 1

   Switch to Write for step one only

   After the plan looks sane, switch to Write and say: “Execute step 1 only: add validation in the target file; show the diff and wait before other steps.”

2. 2

   Accept per hunk, not Accept All

   Read each proposed change in the diff view. Use Accept on one file at a time. If Cascade proposes shell commands (npm test, pytest), read the command and output before Allow.

3. 3

   Finish with git diff

   Run git diff yourself. Wrong change? git restore on touched paths. Only then start Write on step 2—or open a New Chat if context feels muddy (see refresh guide).

# Plan → Write workflow · Windsurf Cascade · 2026-10-15
cd /path/to/your/repo && git status
# Cascade: Plan → "@src/parser.ts — plan validation only, no edits"
# Switch Write → "Step 1 only; show diff; wait"
# Review hunks → git diff → git restore .   # if needed

Mode picker cheat sheet

Suggested workflow: Plan with tight @ scope → Write step 1 → per-hunk Accept → git diff → next step or new chat. Commands and credits: official Windsurf docs for your build.

Vs the install guide

Install covers download and sign-in; this page covers Plan → Write after Cascade already runs.

Vs refresh guide

Refresh fixes updates and stale threads; workflow picks modes for reviewable diffs.

Scope

Cascade workflow only—not wbmeet meeting setup.

Questions worth checking