plan-mergelisted

# Plan Merge Merge two (or more) plan documents into one. The output is a single plan where overlapping goals are resolved, phases are re-sequenced into a coherent order, and the originals are archived — not deleted — so their context remains inspectable. This skill is **conversational**. It does not auto-merge. It surfaces the decisions a human has to make (which plan is the spine, how to resolve overlaps, how to order dependencies) and then writes the merged plan only after those decisions are settled. ## When to use - Two plans in `documentation/plans/` target related work and the team hasn't decided which one to execute. - One plan describes a *capability* (e.g. "add feature X") and another describes the *infrastructure* that feature needs. They overlap at the seam and need reconciliation. - A plan's phases reference work that is separately planned elsewhere. - An old plan is partially superseded by a newer one and they need to be unified rather than left to rot in parallel. Do NOT use this skill: - To merge a plan with its own code — that's `/repo-update` or direct editing. - To refine a single plan — that's `/plan-review`. - To split a plan into smaller phases — write a new plan. ## Inputs - Paths to two or more plan files (ask if not provided). - Optionally, the target path for the merged plan. Default: `documentation/plans/<descriptive-name>-master-plan.md`. ## Process ### 1. Read both plans in full Do not skim. The overlap that matters is rarely