# Merge Docs

> Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

- Skill: `serpro69/merge-docs-2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add serpro69/merge-docs-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/serpro69/merge-docs-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: serpro69 (https://skillmd.com/u/serpro69)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/serpro69/merge-docs-2

---


# Merge Design Documents

**Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.**

## Conventions

- **Read capy knowledge base conventions** at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md).

## When to Use

You have two feature directories under `/docs/wip/` for the same feature — each with its own design, implementation plan, and task list — and you need to combine them into one coherent set of docs.

## Workflow

**Mandatory order — grounding before merging.** The flow below is strictly sequential. Do not categorize sections, surface contradictions, or write merged content until you have read both feature directories fully and built a codebase-grounded mental model. Merging without grounding produces decisions based on prose clarity rather than codebase reality — the wrong tiebreaker.

See [merge-process.md](./merge-process.md) for the detailed steps.