Skip to main content
skill CX Codex

merge-docs — Claude Code skill: merge two design docs

merge-docs combines two doc sets for one feature into one: design, plan and tasks. Handy when design ran twice and you need a single version to build from.

no license ★ 155 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add serpro69/claude-toolbox --skill merge-docs -a claude-code
Open on GitHub

What merge-docs does

The skill takes two write-ups of the same feature, whether they compete or complement each other, and produces one set of documents from them: a design doc, an implementation plan, a task list. That happens when the design step ran more than once and /docs/feat/wip/ now holds two folders about the same thing.

The order is fixed. Both folders get read in full first, and the skill builds a picture of how the project's code actually works. Only then does it sort sections, flag contradictions and write the merged text. Skip that grounding and the merge picks whichever document reads better — the wrong tiebreaker. Steps live in merge-process.md next to SKILL.md; the knowledge-base conventions sit in shared-capy-knowledge-protocol.md.

It works on a pair: two feature folders under /docs/feat/wip/, each carrying its own design, plan and task list. Docs kept elsewhere need to be moved into that layout first. Without reading the code, the merge follows the smoother prose instead of the project, which is the mistake this skill exists to prevent.

What it helps with

  • merge two competing design docs for one feature
  • find contradictions between two implementation plans
  • build one task list from two parallel design runs
  • decide which doc version matches the code

Example prompts for the agent

  • Merge the two billing-retry feature folders under /docs/feat/wip/ into one set of docs.
  • Compare the two design docs for this feature and list where they disagree.
  • Combine the design, plan and task list from both runs into a single set.

How to install merge-docs

1Skills CLI (Vercel)

npx skills add serpro69/claude-toolbox --skill merge-docs -a claude-code

2Manually: put the files in place

~/.claude/skills/merge-docs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/merge-docs/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about merge-docs

How do I install merge-docs in Claude Code?

Run npx skills add serpro69/claude-toolbox --skill merge-docs -a claude-code. The skill file lands at ~/.claude/skills/merge-docs/SKILL.md.

What does merge-docs do?

It compares two sets of docs for one feature and turns them into a single set: design, implementation plan, task list. The codebase is read first, so contradictions get settled by the code rather than by which text sounds better.

Does the skill work in Codex?

Yes. Install it with npx skills add serpro69/claude-toolbox --skill merge-docs -a codex; the file goes to .agents/skills/merge-docs/SKILL.md.

Similar skills

All skills for Writing and docs →

From the same set30

The whole set →
example-skill example-skill is a Claude Code skill that validates input data and builds a conformance report. It runs during diff-skill evaluation tests. CX Codex +1 ★ 155repo stars default The default command checks an answer with Chain-of-Verification: it creates fact-checking questions, answers them separately, then revises the result. CX Codex +1 ★ 155repo stars default default validates code against feature design files to catch spec deviations, missing requirements, and outdated docs. CX Codex +1 ★ 155repo stars review-tool The review-tool skill checks tool configuration files against project schemas and reports violations. Use it when you need a full scan that continues after errors appear. CX Codex +1 ★ 155repo stars isolated isolated — a command that runs code review through a separate spec-reviewer sub-agent with no authorship bias. Surfaces gaps between documentation and implementation by comparing them from scratch. CX Codex +1 ★ 155repo stars isolated The command checks an answer by assigning separate verification questions to isolated sub-agents. Use it to review factual claims or investigate code in a project. CX Codex +1 ★ 155repo stars diff-skill Diffs two revisions of a skill's markdown instructions and flags the edits that weaken a rule or add avoidable complexity. Useful before you accept changes to a skill you rely on. CX Codex +1 ★ 155repo stars isolated Runs an isolated multi-model code review on git changes. Evaluates security, compatibility, and design rules across separate reviewers. CX Codex +1 ★ 155repo stars

Project sponsors

Companies that keep this analytics open