team-coordination

Structure multi-agent debates into synthesized decisions with documented disagreements.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill team-coordination-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-coordination
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/agents/plugins/agent-teams/skills/team-coordination
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill team-coordination-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of unstructured multi-agent disagreement by providing structured debate protocols that produce well-examined conclusions instead of noise or fake consensus.

Core Features & Use Cases

  • Three-phase team debates: run independent investigation, cross-examination, then synthesis that records convergence and divergence.
  • Cross-examination patterns: use evidence, assumption, magnitude, alternative explanation, and so-what challenges to stress-test claims.
  • Consensus vs. dissent documentation: explicitly format resolved disagreements, unresolved uncertainties, and dissenting views so they are auditable and decision-ready.
  • Verdict frameworks: end debates with a clear BUILD/DON’T BUILD style recommendation (including conditional and evidence-insufficient outcomes).

Quick Start

Use team-coordination to coordinate a PRD stress test where different reviewers attack the same proposal from market-fit, feasibility, and scope angles, then synthesize a final verdict that documents both convergence and unresolved tensions.

Frequently Asked Questions about team-coordination

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

FAQPage Schema
How do I structure multi-agent debate to synthesize evidence into team decisions?

You can stress test a PRD review by assigning different agent roles to attack the same proposal from market-fit, feasibility, and scope angles, then synthesize a final BUILD or DON'T BUILD verdict documenting unresolved tensions.

What cross-examination patterns work best for stress testing parallel research findings?

Effective cross-examination patterns for parallel research include evidence, assumption, magnitude, alternative explanation, and so-what challenges to stress-test claims and prevent fake consensus during synthesis.

Does team workflow consensus building require specific agent roles for competitive war rooms?

Structured disagreement requires agents to conduct phased independent investigations and use one-round evidence-based cross-examination, explicitly formatting resolved disagreements, unresolved uncertainties, and dissenting views for auditable records.

How do I document consensus vs dissent when synthesizing cross-examination results?

Document consensus versus dissent by explicitly formatting resolved disagreements, unresolved uncertainties, and dissenting views during final synthesis, ensuring the team workflow produces auditable and decision-ready records.

When should I avoid using structured disagreement for idea validation?

Avoid using structured disagreement for idea validation when you lack sufficient evidence for independent investigation, as the synthesis framework requires evidence-based cross-examination to produce a clear verdict instead of fake consensus.