merge-protocol

Consolidates and deduplicates parallel subagent results into a single conflict-resolved report.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill merge-protocol-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-protocol
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/merge-protocol
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill merge-protocol-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple subagents run in parallel within one Work Block, their outputs overlap, conflict, and duplicate findings. This Skill collects all subagent results, deduplicates findings, resolves verdict conflicts, and produces one consolidation report so Control Tower can proceed to SSOT sync with clean input. ## Core Features & Use Cases - Result Collection & Deduplication: Gathers all subagent reports, groups findings by file:line, and merges identical findings while crediting every discoverer. - Conflict Resolution: Applies a priority rule table (BLOCKED > ISSUES > PASS) to reconcile contradictory verdicts, escalating unresolvable conflicts as a hard stop. - Severity Classification & Reporting: Classifies findings into P0/P1/P2/Accepted tiers and writes a consolidation report to docs/reports/ with a PROCEED, ESCALATE, or RERUN decision. - Use Case: After three parallel review subagents finish a Work Block, run the merge protocol to combine their findings, resolve one conflicting verdict on a shared file, and hand a single consolidated report to the SSOT sync closeout step. ## Quick Start Run the merge protocol for Work Block WB-12 at Stage 2 to consolidate all completed subagent results into a consolidation report.

Frequently Asked Questions about merge-protocol

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

FAQPage Schema
How do I merge results from multiple parallel subagents?▼

Run the merge protocol after all subagents complete. It collects reports from docs/reports/, deduplicates findings by file:line, resolves verdict conflicts using priority rules, and writes a consolidation report with a PROCEED, ESCALATE, or RERUN decision.

How are conflicting verdicts between subagents resolved?▼

Conflicts resolve by priority: BLOCKED beats ISSUES and PASS, and ISSUES beats PASS. Identical findings are deduplicated with all discoverers credited. Contradictory evidence that cannot be reconciled triggers a hard stop and escalation to Control Tower.

When should the merge protocol be skipped?▼

Skip it when only a single subagent ran, when execution was purely sequential with no parallel branches, or when the Work Block involved just one agent. In those cases use the subagent output directly without consolidation.

What happens when a subagent conflict cannot be resolved?▼

Unresolvable conflicts cause a hard stop. Both conflicting reports are quoted and escalated to Control Tower, and the workflow waits for a human decision before proceeding to SSOT sync closeout.

Does the merge protocol discard low-priority findings?▼

No. Findings are never discarded. Even accepted risks are documented with rationale in the consolidation report, and every merged finding retains traceability to its source agents as part of the audit trail.