Chris Creates with AI
Back to Guides
Beginner3 min readGuides

Complete Mode Windsurf Rule File (Copy-Paste Ready)

The complete Windsurf rule file for Complete Problem Solving Mode—ready to copy into your .windsurf/rules directory.

Published October 29, 2025

Complete Mode Windsurf Rule File

Copy the content below and save it as .windsurf/rules/complete-mode.md in your project root.

Installation Steps

  1. Create the directory: .windsurf/rules/ in your project root
  2. Create a new file: complete-mode.md in that directory
  3. Copy all the content from the code block below
  4. Paste it into the file and save
  5. In Windsurf Rules UI, set activation to Manual
  6. Test with @complete-mode in any Cascade conversation

Rule File Content

Copy everything below this line:

# Universal Complete Problem Solving Mode

**Purpose**: Prevent early "one-and-done" fixes. Enforce multi-pass discovery, explicit acceptance gates, and an audit trail across *any* domain (software, ops, data, research/writing, product/UX, etc.).

**How to invoke (Manual)**: `@complete-mode`

**Model Decision hint (optional)**: Use when the ask implies end-to-end resolution with acceptance criteria or "find all causes / fix in order."

**Quick use steps (mid-thread)**

1. Call: `@complete-mode`  
2. Paste **Task** and **Context** (one or two lines each).  
3. Paste **one** of the **DONE overlays** (below) for your domain.  
4. (Optional) Add **toggles** like `scope:… depth:… risk_tolerance:… strict:on`.  
5. Let the loop run until **all gates** are proven *in-message*.

---

## Re-anchor — Universal Complete Problem Solving Mode

**Task** = `<what we're doing, in one sentence>`  
**Context** = `<where/who this affects; constraints/tools available>`

### Definition of DONE (Acceptance Gates — all required)

- **Objective met**: `<measurable outcome>`
- **Independent validation**: `<how to verify externally or by a second method>`
- **Zero criticals**: Problem Register has 0 P0/P1 items remaining (P2 allowed only with rationale)
- **Evidence pack**: attach links/snippets/artifacts with timestamps sufficient for audit/replay

### Operating Loop (repeat until DONE)

1. **Discover** → Append to **Problem Register** (ID, Severity P0–P2, Category, Evidence, Root Cause, Dependencies, Proposed Action, Confidence).  
2. **Plan** → Order by dependency/impact; select minimal, reversible next actions.  
3. **Execute** → Apply the action(s); capture exact commands/steps/decisions (diffs where applicable).  
4. **Verify (Primary)** → Show direct proof against the objective (metrics/logs/tests/results/screenshots/links).  
5. **Verify (Independent)** → Corroborate via a *different* method/source (alternate dataset/monitor, stakeholder confirmation, replication, counterfactual/simulation).  
6. **Re-scan** → Run a NEW discovery pass using at least **two different methods** than last pass (e.g., log analysis, static review, sampling, experiment, stakeholder interview, contract/spec reading, control-run/simulation).  
7. **Update Registers** → Mark statuses; add new items if found. **Do not claim DONE** unless all gates are satisfied.

### Registers & Outputs (strict)

- **Problem Register**: running list with statuses (Resolved / Partial / Blocked + explicit blocker).  
- **Action Log**: exact diffs/changes or decision notes, with before/after metrics.  
- **Final Status**: DONE or NOT DONE; if not, list blockers + next concrete steps.  
- **What to Watch**: residual risks (1–5 bullets) + monitoring plan.

### Anti-Shortcuts

- If only one issue is found in a pass, perform at least **two more** discovery passes before claiming DONE.  
- If access is missing (e.g., private logs, legal doc), state the **exact ask** and continue narrowing with what you have.  
- Never restate generic tips; every claim must be tied to **evidence or a cited source**.

### Mode Toggles (inline, anytime)

- `scope:<area>` (e.g., `scope:runtime` \| `scope:policy` \| `scope:analysis` \| `scope:ux`)  
- `depth:shallow|normal|deep`  
- `risk_tolerance:low|med|high`  
- `max_actions:<n>`  
- `strict:on` (refuse to claim success without all gates)

---

## Problem Register & Action Log templates

**Problem Register (copy once; keep updating):**

| ID | Sev | Category | Evidence (short) | Root Cause | Proposed Action | Status | Confidence |
| ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
| P-01 | P0 |  | `<signal/log/metric>` |  |  | Resolved/Partial/Blocked | 0.0–1.0 |

**Action Log (append per pass):**

### Pass N — Action Log

- Change: `<diff/ref/command>`  
- Before → After: `<metric/log/test summary>`  
- Verification (Primary):  
- Verification (Independent):  
- New signals found? `<yes/no + notes>`

**Final Status stub:**

**FINAL STATUS:** DONE ✅ (all gates satisfied)  
**WHAT TO WATCH:** `<3–5 bullets>`  
**FOLLOW-UPS:** `<debt items, next iteration>`

---

## DONE overlay — Software/DevOps

Use for services, deploys, infra work.

- **Cloud health**: primary endpoint (e.g., `/healthz`) returns **200** for **≥30 minutes**; process has **0 unexpected restarts**.  
- **Logs clean**: last **2 minutes** of runtime logs show **no errors above INFO**.  
- **Local gates**: build **+** tests **+** type/lint pass with **0 failures**.  
- **Zero criticals**: Problem Register has 0 P0/P1 remaining.  
- **Evidence pack**: health URL/link/screenshot, log excerpt, test summary, commit/PR refs.

**Suggested toggles**: `scope:start-command`, `scope:db-migrations`, `scope:config`, `depth:deep`, `risk_tolerance:low`.

---

## DONE overlay — Data/Analytics

Use for analyses, pipelines, experiments.

- **Objective met**: target metric achieved (state exact threshold/OKR).  
- **Statistical validity**: effect validated (e.g., **p < 0.05** or CI excludes 0); sample sizes adequate.  
- **Reproducibility**: notebook/script + **dataset hash/snapshot** provided; re-run reproduces result.  
- **Zero criticals**: Problem Register has 0 P0/P1 remaining.  
- **Evidence pack**: plots/tables, stats summary, code path + data hash, dashboard link.

**Suggested toggles**: `scope:metrics`, `scope:experiment-design`, `scope:data-quality`, `depth:deep`.

---

## DONE overlay — Research/Writing

Use for briefs, memos, docs.

- **Claims supported**: ≥ **3 primary/authoritative sources** for key assertions; **quotes + citations** included.  
- **Counterevidence**: major counterarguments identified and addressed or scoped with rationale.  
- **Clarity/completeness**: executive summary + key takeaways + limitations present.  
- **Zero criticals**: Problem Register has 0 P0/P1 remaining (e.g., unverified claim = P1).  
- **Evidence pack**: bibliography with links, quoted snippets, notes on source reliability.

**Suggested toggles**: `scope:citations`, `scope:counterarguments`, `risk_tolerance:low`.

---

## DONE overlay — Product/UX

Use for prototypes, flows, usability.

- **Ship/prototype**: interactive artifact available (link or build); core flow implemented.  
- **Usability proof**: task success rate ≥ **target** on **N** users (state target & N) *or* validated heuristic checklist.  
- **Acceptance notes**: known limitations + next iteration scope documented.  
- **Zero criticals**: Problem Register has 0 P0/P1 remaining (blocking defects, broken nav).  
- **Evidence pack**: prototype link, task metrics/notes, decision log.

**Suggested toggles**: `scope:core-flow`, `scope:accessibility`, `depth:normal`.

---

### Suggested activation settings (set in Rules UI)

- **Activation**: Manual (primary). Optionally enable Model Decision with description: "Use for end-to-end completion with explicit acceptance gates."  
- **Globs**: leave blank (universal), or add selectively per repo (e.g., `**/*.sh`, `**/*.ipynb`) if you want auto-activation on certain artifacts.

Verification

After saving the file, verify it's working:

  1. Open a Cascade conversation
  2. Type @complete-mode
  3. You should see autocomplete suggesting your rule
  4. Paste a task and context to test

Example test:

@complete-mode

Task = Test that Complete Mode rule is active
Context = Testing installation, no real problem to solve

[DONE overlay — Software/DevOps]
- Rule recognized and activated
- Cascade follows the loop structure
- Evidence: This response includes Problem Register

strict:on

If Cascade responds with the Complete Mode structure (Problem Register, passes, etc.), installation succeeded!

Troubleshooting

Issue: @complete-mode doesn't autocomplete

Fix:

  1. Verify file is at .windsurf/rules/complete-mode.md (exact path)
  2. Restart Windsurf
  3. Check Rules UI to confirm it appears

Issue: Rule activates but isn't followed

Fix:

  1. Add strict:on to your prompt
  2. Ensure you included a DONE overlay (required for gates)
  3. Be explicit: "Follow the complete-mode rule structure"

Issue: File path unclear

Fix:

  • If your project root is /home/user/myproject/
  • Create: /home/user/myproject/.windsurf/rules/complete-mode.md
  • On Windows: C:\Users\YourName\Projects\myproject\.windsurf\rules\complete-mode.md

Next Steps

  1. Install the rule using steps above
  2. Test on a simple problem to verify activation
  3. Customize the overlays for your team's standards
  4. Share with teammates and establish when to use it
Back to GuidesExplore Prompting Techniques