refinement

Refine ambiguous product specifications into testable work items via structured multi-agent debate.

11|5|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/rbergman/dark-matter-marketplace --skill refinement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refinement
Source: https://github.com/rbergman/dark-matter-marketplace/tree/main/plugins/teams/skills/refinement
Command: npx skills add https://github.com/rbergman/dark-matter-marketplace --skill refinement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Team-based adversarial spec refinement helps convert ambiguous requirements into concrete, testable work items using persistent Agent Teams.

Core Features & Use Cases

  • Persistent multi-agent debate to surface gaps and bind scope.
  • Role-based team composition (Analyst, Proposer, Advocate, Judge) with structured phases.
  • Generates concrete implementation details and acceptance criteria for product specs.
  • Use Case: For a vague feature, run a refinement debate to produce a clear scope and testable tasks.

Quick Start

Activate refinement by invoking the Team Refinement skill to start a live debate on a provided specification and capture the synthesized, testable spec.

Frequently Asked Questions about refinement

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

FAQPage Schema
How do I refine ambiguous product specifications into testable work items?

Refine ambiguous product specifications by running a live, adversarial debate among role-based agents that surfaces gaps and binds scope, ultimately generating concrete acceptance criteria and testable tasks.

What is adversarial spec refinement and how does it work for feature scoping?

Adversarial spec refinement is a structured debate process where role-specific agents—an Analyst, Proposer, Advocate, and Judge—challenge fuzzy requirements to produce explicit risk tags and a clear, testable feature scope.

How do I turn a vague feature spec into concrete acceptance criteria for engineering teams?

Turn a vague feature spec into concrete acceptance criteria by invoking a multi-agent refinement debate that synthesizes conflicting perspectives into structured, testable implementation details for engineering.

Does multi-agent debate help with product scope refinement across design and engineering teams?

Multi-agent debate helps product scope refinement by applying structured, role-specific contributions from design, engineering, and product perspectives to surface risks and bind scope into testable work items.

Can I use agent teams to surface gaps and bind scope in complex feature requirements?

You can use persistent agent teams to surface gaps and bind scope in complex requirements through structured debate phases that generate explicit acceptance criteria and testable implementation details.

What are the limitations of using automated debate for product spec refinement?

Automated debate for product spec refinement relies entirely on the initial input quality and may not capture undocumented domain knowledge, requiring human review to validate generated acceptance criteria and risk tags.