Merge Design Documents
SkillDocs & knowledgeCompare 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Merge Design Documents skill
What this skill tells your AI
The instructions your AI receives, as published by serpro69/claude-toolbox in kodex-plugin/skills/merge-docs/SKILL.md and read by ahel’s review.
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/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 for the detailed steps.
Signals
- GitHub stars
- 149
- Forks
- 31
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
merge-docs- Source
- github.com/serpro69/claude-toolbox