Where it has worked is to have Qwen not just write the proposed solution, but also include all the files it consulted and why it did or didn’t consider them. The documentation is often longer than the patch, but it lets me prompt Claude differently. I tell Claude to challenge the implementation and find holes, edge cases and things not considered. Maybe it’s my imagination, but Claude kicks it into another gear when you tell it to evaluate the results of another model.
Maybe this is a pure preference but I find Qwen to be bad at UI and these edits Claude will often let go.
One thing I haven’t tried, but will at some point is to hand Qwen all my half assed ideas and things I can’t be bothered to spec out. Probably not to take the output, but to help me draft a more complete issue because it’s only costing me electricity.