Merge docs
Skill serpro69/claude-toolbox/klaude-plugin/skills/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.From its SKILL.md
npx -y skills add serpro69/claude-toolbox --skill merge-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.2 KB, 197 tokens by cl100k_base, as published. Nobody here has run it
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.
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 for the detailed steps.
What ships with it: 2 files
5.8 KB alongside SKILL.md