From dm-team
Run team-based adversarial refinement on a bead or spec using Agent Teams debate
How this command is triggered — by the user, by Claude, or both
Slash command
/dm-team:refine bead ID or spec file pathThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /refine Run team-based adversarial spec refinement. Arguments: $ARGUMENTS ## Protocol ### 1. Parse Target - Bead ID -> `bd show <id>` - File path -> read file - No args -> check conversation for current spec context ### 2. Assess Complexity - **xs/s** -> "This doesn't need refinement. Proceed to implementation." - **m** -> "Medium complexity -- using 2-phase dm-work:dialectical-refinement instead." Run /dm-work:refine. - **l/xl** -> Proceed with team refinement. ### 3. Gather Context Read target spec, related files, existing beads for the project. ### 4. Create Team Spawn Agent...
Run team-based adversarial spec refinement.
Arguments: $ARGUMENTS
bd show <id>Read target spec, related files, existing beads for the project.
Spawn Agent Team with Analyst (haiku), Proposer (opus), Advocate (opus). Lead acts as Judge.
Execute the debate protocol as described in the refinement skill:
Synthesized spec in standard format:
## Introduction
## Scope
## Acceptance Criteria
## Out of Scope
## Appendix A: Project Context (if needed)
If input was a bead, update with refined spec, add refined label.
Dismiss teammates after synthesis is complete.
npx claudepluginhub rbergman/dark-matter-marketplace --plugin dm-team/spec-panelReviews and improves specification content using a multi-expert panel of renowned engineering specialists, producing consolidated findings and enhanced specs.
/sc-spec-panelReviews and improves software specifications using a multi-expert panel of renowned specialists, producing enhanced specs with prioritized recommendations.
/spec-teamGenerates a team execution spec from the current brainstorming session and saves it as a dated Markdown file in specs/YYYY-MM-DD-<name>.md.
/devkit.spec-reviewInteractively reviews functional specification quality by asking up to 5 targeted questions to identify ambiguities, gaps, and improvements, then integrates responses into the spec with a final report.
/specGenerates or refines Choo Choo Ralph spec files (.choo-choo-ralph/*.spec.md) from plan files or conversation context, using parallel sub-agents for codebase and tech research.
/techspecInforms users this command is deprecated, directs to /humaninloop:plan for unified technical specification workflow, and stops execution.