serpro69/claude-toolbox-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.
npx skills add https://github.com/serpro69/claude-toolbox --skill merge-docs<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh -->
Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.
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.
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.
Take serpro69/claude-toolbox-merge-docs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.