Transform ambiguous specs into implementable work items through live adversarial debate using Agent Teams. Evolves dm-work:dialectical-refinement from sequential pipeline to simultaneous multi-agent debate. Use for l/xl complexity tasks.
Transforms ambiguous specifications into concrete work items through multi-agent adversarial debate.
npx claudepluginhub rbergman/dark-matter-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Team-based adversarial spec refinement using Agent Teams. This evolves dm-work:dialectical-refinement from sequential pipeline to live debate.
The original dialectical-refinement runs 5 sequential phases (Analyst->Proposer->Advocate->Scope Lock->Judge) where each phase sees only the previous output. This prevents self-reinforcing mistakes but loses the back-and-forth of genuine argument. With Agent Teams, debaters are persistent -- the Advocate can push back on the Proposer while the Proposer is still formulating, creating richer adversarial tension.
| Complexity | Mechanism |
|---|---|
| xs/s | Skip refinement entirely |
| m | Use dm-work:dialectical-refinement (2-phase, lightweight) |
| l/xl | Use refinement (full debate) |
| Role | Teammate | Model | Purpose |
|---|---|---|---|
| Analyst | Teammate 1 | haiku | Surface ambiguity, identify gaps, tag protected items |
| Proposer | Teammate 2 | opus | Propose simplifications and cuts with confidence levels |
| Advocate | Teammate 3 | opus | Challenge cuts, defend scope, suggest cheap additions |
| Judge | Lead | opus | Moderate debate, enforce scope lock, synthesize final spec |
Same as dm-work:dialectical-refinement — Core Workflow, Agent Primitives, User-Requested Features, Token Efficiency, Structured Output. Tag these early; Proposer does not propose cutting them.
Same as dialectical-refinement for compatibility:
## Introduction
[What + Why in 2-3 sentences]
## Scope
[What's being built]
## Acceptance Criteria
[Testable outcomes]
## Out of Scope
[Explicit boundaries]
## Appendix A: Project Context (if needed)
[Token-efficient big picture: ~100-200 words max]
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.