Zscole Adversarial Spec
Adversarial-spec is a Claude Code plugin for the Validate phase that refines PRDs and technical specs through multi-LLM debate until models consensus.
by zscole · github.com/zscole/adversarial-spec
Add adversarial-spec when you want PRDs and technical specs stress-tested by debating models until they agree before you commit engineering time.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install zscole-adversarial-spec@zscole/adversarial-specBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:zscole/adversarial-spec") and the paste-ready config with skillselion.get_install_config("plugin:zscole/adversarial-spec").
What it does
Adversarial-spec is a Claude Code plugin that helps solo builders and indie PM-dev hybrids produce sharper specs before code lands. Rather than accepting the first draft from one model, it iteratively refines product requirements and technical specifications by debating between multiple LLMs until they converge on consensus. That fits the Validate phase and scope subphase as the primary shelf, because the output is a tighter boundary on what to build and how—but the artifact also feeds Build pm and docs work once engineering starts. With one focused plugin and solid GitHub traction, it is an intermediate tool: you should arrive with a rough PRD or feature outline worth arguing about. It complements brainstorming or writing-plans style skills by adding adversarial quality control, not by replacing your voice as the final decision maker.
Highlights
- Single plugin that runs iterative multi-LLM debate on product and technical specifications
- Continues refinement until participating models reach consensus on the spec
- Targets PRDs, technical specifications, and multimodel adversarial review
- Claude Code-native loop so you stay in the agent instead of copy-pasting between chat tools
Why builders use it
Single-model specs hide contradictions and fuzzy requirements, so solo builders ship the wrong thing after trusting a polished-but-unexamined PRD.
After registration, you get iteratively debated specifications with fewer unresolved conflicts before implementation begins.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 519 stars, 0 votes.
FAQ
Who is zscole-adversarial-spec for?
It is for Claude Code users drafting PRDs or technical specifications who want adversarial, multi-model review without manual parallel chats.
When should I use zscole-adversarial-spec?
Use it after a first spec draft and before heavy build work, when requirements feel plausible but untested against alternative interpretations.
How do I add zscole-adversarial-spec to my agent?
Install the zscole/adversarial-spec plugin in Claude Code, enable its single plugin entry, supply your draft PRD or technical spec, and run the iterative debate-to-consensus flow in session.
Comments
Share how you use zscole-adversarial-spec, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.