Agent skill · Workflow & Productivity

windsurf-core-workflow-a

Execute Windsurf''s primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-core-workflow-a --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(npm:*)Grep
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/windsurf-core-workflow-a/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Windsurf Core Workflow A — Cascade Write Mode ## Overview Cascade Write mode is Windsurf's primary productivity tool. It acts as an autonomous agent that can create files, modify code across multiple files, run terminal commands, install dependencies, and debug errors -- all from a single natural language prompt. This is the "money-path" workflow for Windsurf users. ## Prerequisites - Windsurf IDE with Cascade enabled - `.windsurfrules` configured (see `windsurf-sdk-patterns`) - Git initialized with clean working tree ## Instructions ### Step 1: Create a Git Checkpoint Always commit or stash before a Cascade session. Cascade writes directly to your files. ```bash git add -A && git commit -m "checkpoint: before cascade session" # Or for uncommitted work: git stash push -m "pre-cascade stash" ``` ### Step 2: Open Cascade in Write Mode Press **Cmd/Ctrl+L** to open the Cascade panel. Ensure "Write" mode is selected (not "Chat"). Write mode allows Cascade to: - Create and modify files - Run terminal commands (with Turbo or per-command approval) - Install dependencies - Read terminal output for debugging - Open browser previews ### Step 3: Write an Effective Prompt Structure your promp

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Create a Git Checkpoint
  5. Step 2: Open Cascade in Write Mode
  6. Step 3: Write an Effective Prompt
  7. Step 4: Review Cascade's Plan and Execution
  8. Step 5: Iterate on Errors
  9. Step 6: Use @ Mentions for Precision
  10. Output
  11. Error Handling
  12. Examples
  13. Full-Stack Feature
  14. Refactoring Task
Commands it runs
git add -A && git commit -m "checkpoint: before cascade session"
Or for uncommitted work:
git stash push -m "pre-cascade stash"
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the windsurf-core-workflow-a skill do?

Execute Windsurf''s primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-core-workflow-a --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going