uc-merge

Merge draft UseCase files into a unified design document with a merge report.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill uc-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uc-merge
Source: https://github.com/GoGradually/usecase-driven-design-skills/tree/main/usecase-driven-design/skills/uc-merge
Command: npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill uc-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges multiple UseCase draft files into a single, coherent main design document, ensuring consistency and traceability across the project.

Core Features & Use Cases

  • Reorders UC IDs and consolidates drafts into a unified design.
  • Integrates domain models, state models, and external/internal use cases with deduplication and conflict checks.
  • Regenerates Mermaid diagrams and updates the main document along with a dedicated merge report.

Quick Start

Place draft UseCase files under drafts/ and run this skill to merge them into the main design document.

Frequently Asked Questions about uc-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge multiple UseCase draft files into a single design document?

To merge multiple UseCase drafts into a single design document, place your draft files in the drafts directory. The workflow consolidates them into one coherent specification, outputting the unified design at docs/usecase/[project-name]-usecase-design.md.

What happens to UseCase IDs and domain models when consolidating drafts?

When consolidating drafts, the merge process reorders UseCase IDs and integrates domain models with deduplication and conflict checks. This ensures the unified design document maintains consistency and traceability across all integrated components.

Can I automatically regenerate Mermaid diagrams when merging UseCase drafts?

Yes, you can regenerate Mermaid diagrams when merging UseCase drafts. The merge workflow automatically updates and regenerates the diagrams within the main design document to reflect the consolidated state and domain models.

How does the merge process handle state model consolidation and traceability?

State model consolidation is handled by integrating and unifying state models from multiple drafts. The process ensures traceability by generating a dedicated merge report alongside the main document, detailing all changes and conflicts resolved.

Do I need any external dependencies to unify external and internal UseCase drafts?

You do not need any external dependencies to unify external and internal UseCase drafts. The workflow independently handles deduplication, conflict checks, and consolidation directly within your project environment.

Why are my UseCase draft conflicts not resolving during the merge?

UseCase draft conflicts may persist if the domain models or state models contain unresolved discrepancies. The merge process performs conflict checks and outputs a merge report to help you trace and manually address any remaining issues.