wf-docker-documentation-migration-method

Migrate legacy documentation into canonical Delphi templates with gap analysis and milestones.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-documentation-migration-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-docker-documentation-migration-method
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/wf-docker-documentation-migration-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-documentation-migration-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate ad-hoc/legacy documentation into canonical Delphi templates with gap analysis, milestones, and team handoff.

Core Features & Use Cases

  • Gap analysis to identify missing sections, inconsistencies, and alignment with Delphi templates.
  • Template-driven migration across modules, roadmaps, and screens with governance handoff points.
  • Progressive milestones and task lists to support cross-team collaboration and handoff.

Quick Start

Run the migration workflow to convert temporary docs into canonical Delphi templates and generate milestone-driven roadmaps.

Frequently Asked Questions about wf-docker-documentation-migration-method

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

FAQPage Schema
How do I migrate legacy documentation into canonical templates with gap analysis?

To migrate legacy documentation into canonical templates with gap analysis, run the migration workflow to inventory source materials, scope map modules, identify missing sections, and generate updated docs with governance handoff points.

What is the best way to convert scattered scratch specs and prototype notes into structured roadmaps?

Converting scattered scratch specs and prototype notes into structured roadmaps requires template-driven migration that performs gap analysis, establishes governance, and generates progressive milestones to support cross-team handoff.

How does gap analysis work when migrating domain docs across modules?

Gap analysis identifies missing sections, inconsistencies, and alignment issues against canonical Delphi templates across modules, roadmaps, and screens to ensure complete documentation migration with established governance.

Do I need access to source documents and route ownership guidance to migrate documentation?

Yes, documentation migration requires access to source documents, canonical templates, and route ownership guidance to execute inventory, scope mapping, gap analysis, and canonical doc generation steps effectively.

Can I use template-driven migration to establish team handoff points for early domain docs?

Template-driven migration establishes team handoff points for early domain docs by generating progressive milestones and task lists that support cross-team collaboration and structured governance across modules and screens.

What are the limitations of migrating ad-hoc documentation into canonical templates?

Migrating ad-hoc documentation into canonical templates requires complete access to source materials and route ownership guidance; without established canonical templates and ownership structures, gap analysis and handoff milestone generation cannot execute accurately.