What problem does it solve? When you analyze several related requirement documents separately, you end up with overlapping, duplicated, or contradictory requirement specs that no planner can build from directly. This Skill merges 2+ already-confirmed ORC analyses into a single reconciled requirement context, proving that no source requirement was lost in the merge. ## Core Features & Use Cases - Requirement reconciliation: Pools all source requirements into one table and classifies them as exact duplicates, semantic duplicates, partial overlaps (split, never collapsed), conflicts, or ordering dependencies. - Interactive conflict resolution: Raises every cross-source conflict as a one-at-a-time challenge with a recommended option, checkpointing each decision to combine-decisions.md so nothing is re-asked after a resume. - Conservation gate: Builds a source coverage matrix where every source requirement ID gets exactly one outcome, and blocks handoff until coverage reaches 100%. - Use Case: You analyzed three related feature documents for the same reporting module and chose "pass to context-combiner" at orc-analyze Phase F. The combiner verifies the analyses genuinely overlap, merges them into combined-report.md and combined-requirement-spec.md, and hands the merged spec to the planner unchanged. ## Quick Start Ask the orchestrator to combine the confirmed analyses for the reporting module into a single merged requirement spec before building.
