Notices when a back-and-forth is actually surfacing a real tradeoff and keeps both options alive instead of forcing a premature pick.
Visit skill This is mine — claim it
Listing URL: https://wingmanprotocol.com/skills/preserving-productive-tensions/
Show your listing is live — the card backlinks here and picks up the verified badge automatically once you claim it.
<iframe src="https://wingmanprotocol.com/embed/card/preserving-productive-tensions" width="340" height="170" style="border:0;border-radius:10px" loading="lazy" title="Preserving Productive Tensions — live on WingMan Protocol"></iframe>
Or the one-line script:
<script src="https://wingmanprotocol.com/embed/card.js" data-slug="preserving-productive-tensions" async></script>
Or a README badge:
[](https://wingmanprotocol.com/directory/preserving-productive-tensions?utm_source=badge)
Runs a Socratic back-and-forth to turn a rough feature idea into a fully-formed design before any code gets written.
Fans independent, unrelated failures out to multiple agents to investigate and fix concurrently instead of serially.
Works a written implementation plan in reviewed batches rather than all at once.
Once a feature is done and tested, walks through the merge/PR/cleanup decision instead of leaving the branch dangling.
Handles incoming review feedback with real technical scrutiny rather than reflexive agreement or blind edits.
Searches past Claude Code sessions for the facts, decisions, and context a current conversation needs.