Claude Skill

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.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download serpro69-claude-toolbox-klaude-plugin_skills_merge-docs-4b66a41.zip · 2 KB

Install

skills CLI npx skills add https://github.com/serpro69/claude-toolbox/tree/master/klaude-plugin/skills/merge-docs
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install serpro69-claude-toolbox@llmmart
Git git clone https://github.com/serpro69/claude-toolbox.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole serpro69/claude-toolbox collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Merge Design Documents

Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.

Conventions

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.

Files (claude-toolbox)
  • merge-process.md 5.8 KB
    Loading…
  • SKILL.md 1.2 KB
    ---
    name: merge-docs
    description: |
      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.
    ---
    
    # 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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.