adversarial-spec

Coordinate multi-model debates to generate and refine product specifications.

554|48|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/zscole/adversarial-spec --skill adversarial-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-spec
Source: https://github.com/zscole/adversarial-spec/tree/main/skills/adversarial-spec
Command: npx skills add https://github.com/zscole/adversarial-spec --skill adversarial-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires litellm, and includes scripts (resource) components.

What problem does it solve?

The adversarial-spec skill provides a structured workflow to converge on robust product specifications by simulating debates among multiple language models, surfacing gaps, edge cases, and biases that a single model would miss.

Core Features & Use Cases

  • Multi-model critique rounds for PRD and Technical Specifications to drive comprehensive requirements.
  • Deterministic outputs via standardized prompts, cost tracking, diffing, and session support.
  • Integrates with CLI tools and Bedrock/CLI providers to expose diverse perspectives and robust convergence.
  • Document evolution: stepwise revisions annotated with model feedback and Claude's critiques.
  • Supports final handoff to product, design, or engineering teams with a converged spec and traceable decisions.

Quick Start

  1. Prepare your initial concept or draft.
  2. Run a debate using the debate CLI, selecting available models, and specify document type (prd or tech).
  3. Review model feedback, apply changes, and iterate until all participants agree; export final spec.

Frequently Asked Questions about adversarial-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use multi-model debate to refine a PRD or technical spec?

Refine a PRD or technical spec by running multi-model debates that apply standardized prompts, surface model critiques, and iterate until consensus is achieved. Participants review feedback and apply stepwise revisions to converge on robust requirements.

What is adversarial spec development and how does it improve requirements?

Adversarial spec development simulates debates among multiple language models to generate and refine product specifications. It surfaces gaps, edge cases, and biases that a single model would miss, driving comprehensive requirements.

Does adversarial-spec work with litellm for multi-provider LLM debates?

Yes, adversarial-spec integrates with litellm to leverage diverse CLI and Bedrock providers. This exposes diverse perspectives and robust convergence during multi-model critique rounds for your technical specifications.

How do I track costs and provenance when generating technical specifications via LLM debate?

Generate technical specifications via LLM debate while tracking dependencies, costs, and provenance for audit. The workflow provides deterministic outputs via standardized prompts, cost tracking, diffing, and session support.

Can I export a converged spec for handoff to engineering teams?

Yes, you can export a final converged spec for handoff to product, design, or engineering teams. The export includes traceable decisions and document evolution annotated with model feedback and Claude's independent critiques.

What are the limitations of using multi-LLM debate for spec convergence?

Multi-LLM debate for spec convergence requires iterating until all participants agree, which may incur multiple rounds and associated costs. It depends on litellm integration to expose diverse perspectives from available CLI or Bedrock providers.