Due Diligence Team

Full FREE body

Copy Back to AgentSwarm

Pack body is English. UI language controls translate chrome labels only.

### Due Diligence Team
TYPE: AGENTSWARM WORKFLOW
OBJECTIVE: Execute a coordinated due diligence workflow with independent production, criticism, verification and synthesis.
WHEN TO USE: When the task benefits from decomposition, parallel work and independent checking.
INPUT: Objective; scope; source materials; constraints; required final deliverable.
ORCHESTRATOR: Fix scope, evidence requirements and non-overlapping assignments; prevent duplicate work.
AGENT 1 — DISCOVERY/ANALYSIS: Collect or analyze primary material required for due diligence.
AGENT 2 — SPECIALIST: Perform the core specialist work and document assumptions.
AGENT 3 — CRITIC: Challenge weak reasoning, omissions, contradictions and unsupported claims.
AGENT 4 — VERIFIER: Check factual support, constraints, completeness and handoff quality.
AGENT 5 — SYNTHESIZER: Combine only supported outputs into the final deliverable.
EXECUTION ORDER: Orchestrator → Agents 1 and 2 in parallel where independent → Critic → Verifier → Synthesizer.
PARALLEL RULE: Parallelize only independent work; never parallelize unresolved dependencies.
HANDOFF FORMAT: Findings; evidence/input basis; assumptions; unknowns; risks; recommended next step.
SHARED CONTEXT: Preserve the same objective, constraints, definitions and source set.
CONFLICT RESOLUTION: Preserve disagreement until evidence resolves it; otherwise surface both views and missing evidence.
FINAL OUTPUT: Objective; consolidated findings; verified evidence basis; rejected/uncertain claims; recommendation; risks; next actions.
FAILURE/STOP: Narrow or stop if required access/evidence is absent or execution would require invented capability.
TEAM PROTOCOL FOR “Due Diligence Team”:
- Orchestrator publishes a single source-of-truth brief before agents start.
- Discovery/Specialist/Critic/Verifier must not overwrite each other’s sections; append with agent labels.
- Final synthesis must cite which agent produced each material claim.
- Stop condition: required deliverable complete OR evidence exhausted with open questions listed.
- No fake RUN: humans copy/use this workflow in their own orchestration tool.
HOW TO USE: Run as an orchestration recipe or map roles to BSV agents if real multi-agent execution is supported.
FREE: YES