rule-docker-documentation-migration-model-decision

Migrate temporary documentation into canonical Delphi templates and milestones.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating temporary or legacy documentation into canonical Delphi templates and milestones requires consistent governance, templates, and handoff artifacts to avoid drift and rework.

Core Features & Use Cases

  • Ensures standardized migration workflows across routes and modules.
  • Produces template-based docs, milestones, and team handoffs for delivery.
  • Provides governance checks by applying ownership policies during migration.

Quick Start

Run the Documentation Migration & Expansion Workflow to convert temporary notes into canonical templates and milestones.

Frequently Asked Questions about rule-docker-documentation-migration-model-decision

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

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

Run the Documentation Migration & Expansion Workflow to convert temporary notes into canonical templates, milestones, and team handoffs. This migration process enforces governance and applies ownership policies to prevent drift and rework.

What is the best way to standardize documentation handoffs across modules?

Standardize documentation handoffs by applying canonical templates and milestones across routes and modules. This ensures consistent governance and produces structured delivery artifacts for team transitions.

When do I need to use a documentation migration workflow?

Use a documentation migration workflow when converting temporary or legacy documentation into canonical sources. It ensures ownership policies are enforced and prevents edits to temporary artifacts during the transition.

Does this documentation migration process enforce ownership policies?

Yes, the documentation migration process enforces ownership policies and applies governance checks during migration. This ensures canonical sources are created correctly while avoiding edits to temporary artifacts.

Can I use this workflow to migrate temporary notes across different routes?

Yes, this workflow applies to documentation migration scenarios across routes and modules. It converts temporary notes into template-based docs and milestones to ensure structured team delivery.

Why should I avoid editing temporary artifacts during documentation migration?

Avoid editing temporary artifacts to prevent documentation drift and rework. The migration workflow ensures canonical sources are created instead, providing standardized template-based docs and milestones for reliable delivery.