Tutorial: Using the 'Feedback' system to correct Sudowrite's habit of repeating phrases.

I've been using Sudowrite for a few months now, mainly to help draft internal documentation and process guides. The biggest recurring issue I've hit, and I've seen others mention it in passing, is its tendency to get stuck in a loop and repeat the same phrase or sentence structure multiple times in a single output. It's especially bad when you ask it to expand on a technical point. You'll get something like "This is crucial for deployment automation. This is crucial for pipeline reliability. This is crucial for maintaining uptime."

It's frustrating because the underlying suggestion might be decent, but the repetition makes the text unusable without a full rewrite. I've found the 'Feedback' buttons (Specifically 'Bad Output') to be the most effective tool for correcting this, but you have to be systematic about it. Just hitting the button isn't enough. You need to treat it like training a pipeline.

Here is the workflow I've settled on that has reduced the frequency of these repetitions significantly.

* **Never just regenerate.** When you see the repetition, immediately click the 'Bad Output' thumb-down button.
* **You must provide specific feedback in the text box.** A generic "this is repetitive" doesn't cut it. You need to be an engineer about it.
* **Structure your feedback like a bug report or a linter rule.** Point to the exact offending lines and state the pattern.

For example, if Sudowrite generates this:
```
To ensure a robust deployment, configure the health checks. To ensure a robust deployment, verify the service endpoints. To ensure a robust deployment, review the resource limits.
```

My feedback submission looks like this:
```
The output repeats the introductory clause "To ensure a robust deployment" three times in succession. This is redundant and poor style. Vary the sentence structure or remove the introductory clause after its first use.
```

The key is identifying the *exact repeated segment* and instructing against the *structural pattern*, not just the words. You're essentially giving it a style rule. I've applied this to patterns like "It is important to note that...", "The next step involves...", and "Another key consideration is...".

After providing this detailed feedback, *then* I'll use the 'Rewrite' command on the original source text, often with a more directive prompt like "Expand on the points below without using repetitive introductory phrases. Vary sentence structure." The combination seems to reinforce the correction. It's not a one-time fix; you have to be consistent for a session. Think of it like tuning a Prometheus alert rule – you iterate on the specificity until you get clean results. Over the last few weeks, the repetition in my outputs has dropped by maybe 70%. It's a training process, but it's the only way I've found to make the tool usable for longer-form technical writing.