migration-tools

Migrate legacy flat collaboration diagrams to hierarchical boundary-annotated formats.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/zhongadamwang/pricing-tool --skill migration-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-tools
Source: https://github.com/zhongadamwang/pricing-tool/tree/main/.github/skills/migration-tools
Command: npx skills add https://github.com/zhongadamwang/pricing-tool --skill migration-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy flat (Project 1) collaboration diagrams into hierarchical, boundary-annotated (Project 3) formats while preserving requirement traceability and message flows, enabling safe upgrades.

Core Features & Use Cases

  • Non-destructive batch or per-diagram migration reading inputs collaboration-diagrams.md and collaboration-diagrams.json
  • Applies boundary-detection heuristics and stereotype-classification rules
  • Writes enhanced diagrams and migration logs alongside originals; preserves links and sequences

Quick Start

Run migration-tools to preview or apply changes for all diagrams, reading collaboration-diagrams.md and collaboration-diagrams.json and writing enhanced outputs alongside the originals.

Frequently Asked Questions about migration-tools

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

FAQPage Schema
How do I migrate flat collaboration diagrams to hierarchical formats with boundary annotations?

Migrate flat collaboration diagrams to hierarchical, boundary-annotated formats by applying boundary-detection heuristics and stereotype-classification rules to restructure legacy layouts while preserving original message sequences and requirement traceability.

Can I preview collaboration diagram migration without modifying the original files?

Preview collaboration diagram migration without modifying originals by running the tool in preview mode, which reads existing markdown and JSON inputs and displays the proposed boundary grouping and stereotype classification changes safely.

How does requirement traceability work when upgrading legacy collaboration diagrams?

Requirement traceability during collaboration diagram upgrades works by preserving existing links and message flows throughout the migration process, ensuring the enhanced hierarchical, boundary-annotated outputs maintain the original functional context.

What is the best way to batch migrate multiple collaboration diagrams to boundary-aware formats?

Batch migrate multiple collaboration diagrams by running the tool in batch mode, which processes all diagrams from the input markdown and JSON files simultaneously and applies boundary grouping rules to generate enhanced outputs and a migration log.

Does migrating collaboration diagrams require specific input file formats?

Migrating collaboration diagrams requires specific input file formats, specifically collaboration-diagrams.md and collaboration-diagrams.json files generated by diagram creation tools, to properly apply boundary detection and output enhanced formats.

Are there limitations when applying stereotype classification rules to legacy collaboration diagrams?

Limitations when applying stereotype classification rules include relying on the structural completeness of the input collaboration-diagrams.json and markdown files, as incomplete boundary data or missing message sequences in the legacy source can impact the enhanced hierarchical output accuracy.