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.
Install
/plugin marketplace add serpro69/claude-toolboxThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add serpro69/claude-toolbox --skill merge-docsgit clone --depth 1 https://github.com/serpro69/claude-toolbox.git /tmp/claude-toolbox
mkdir -p ~/.claude/skills
cp -r /tmp/claude-toolbox/klaude-plugin/skills/merge-docs ~/.claude/skills/merge-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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/feat/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.
Details
- Skill name
merge-docs- Repository
- serpro69/claude-toolbox
- Path
klaude-plugin/skills/merge-docs/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Merge Docs skill do?
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.
How do I install the Merge Docs skill?
Claude Code plugin: /plugin marketplace add serpro69/claude-toolbox. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Merge Docs popular?
It lives in serpro69/claude-toolbox, which has 155 GitHub stars and 30 forks, and is included in 1 curated skill list.
Related skills
Brainstorm
155serpro69/claude-toolbox
TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to /kk:design; durable domain glossary/reference kits to /kk:model; implementation and fixes to /kk:implement. Not for nontechnical brainstorming.
Chain of Verification
155serpro69/claude-toolbox
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
Clarify Docs
155serpro69/claude-toolbox
TRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or invoking implementation.
Review Spec
155serpro69/claude-toolbox
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
Linkedin Post Writer
116aakashg/pm-claude-skills
Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.
Status Update Writer
116aakashg/pm-claude-skills
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.