Windsurf Cascade System

Overview (confidence: high)

Windsurf implements the 3-phase cascade pattern — the cleanest workflow separation in the corpus. The envelope format is flat markdown headers (all ##, no nesting), similar to cursor-system-prompt.

Cascade Pattern (confidence: high)

The cascade has three distinct phases, each with a separate output format:

1. Analyze: Understand the request, gather context, identify constraints
2. Plan: Produce architecture plan, list files to modify, detail approach
3. Execute: Implement only after plan approval

Each phase has its own required output structure. The LLM cannot proceed to the next phase until the current one is complete.

Plan-Before-Implement Gate (confidence: high)

Windsurf uses a hard gate — execution is blocked until the user explicitly approves the plan. This is a forcing function for deliberate architecture before implementation. The trade-off is reduced velocity in exchange for increased correctness.

Additional Patterns (confidence: high)

• Parallel tool call maximization: Instruction to identify independent operations and execute them simultaneously — also seen in claude-code-system-prompt
• Full-file overwrite prohibition: Edit only relevant lines, not entire files
• Git-commit-retrieval: Uses git log to understand project history
• Multi-command parallel execution: Chains dependent and independent commands with appropriate separators

Workspace Awareness (confidence: high)

The prompt includes instructions to read workspace state — open files, cursor position, and terminal history — before acting.

Implications (confidence: high)

Windsurf’s cascade pattern is the cleanest workflow separation in the corpus. The hard plan gate is a forcing function for deliberate architecture before implementation — trade-off is reduced velocity for increased correctness.

Sources

• [raw/prompts/articles/taxonomy-synthesis-2026-07-16.md]