跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

ln-26-architecture-migration-planner

Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.

levnikolaevich · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-26-architecture-migration-planner

技能说明


name: ln-26-architecture-migration-planner description: "Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them."

Architecture Migration Planner

Goal: Plan a safe transition from evidenced current architecture to an explicit target, with reversibility limits and recovery actions. Change only the approved migration document; do not execute migrations, edit product code, build a generic task plan, approve delivery, or hide irreversible steps.

Execution contract: The ordered checkboxes are the Definition of Done. Track every item internally as PENDING, PROVEN with concrete evidence, CLEARED with evidence that its condition is absent, or UNPROVEN with a gap; reading, delegation, or tool failure is not proof. Reconcile items after each section. Before returning, resolve all PENDING and count only PROVEN and CLEARED; apply the skill's verdict and approval rules to every gap. Preserve user intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without silently skipping checks. Preserve dependency and safety ordering; otherwise choose the verification method appropriate to each obligation. Treat equivalent user or repository evidence as valid input; another skill, named artifact, or complete lifecycle is not a prerequisite. Preserve source requirement and decision identifiers when available. Bind reused evidence to the relevant source version, dirty changes, configuration, and environment; invalidate only affected claims after a change. On continuation, reconcile the task, existing authorization, current state, and unresolved evidence before resuming. For long work, return a compact continuation record or update an already authorized task artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and authority to perform an external action. Prepare authorized work before any required approval. If an instruction prevents progress, identify its exact source and explain the unresolved boundary; do not invent an approval gate from general caution.

Tool Routing

NeedPreferred capabilityFallback
Current and target statesRepository evidence plus approved architecture artifactsExplicit user-provided states with limitations
Consumers and compatibilityLanguage intelligence, schema tools, config search, telemetry, and direct inspectionConservative inventory marked UNVERIFIED
Data scale and runtime riskProduction metrics, checked-in reports, migrations, and workload evidenceRanges with validation gates before execution
External migration constraintsOfficial vendor migration and compatibility guidanceMark dependent phases BLOCKED or UNVERIFIED
Document mutationMinimal patch to the approved migration-plan artifactReturn BLOCKED when authority or path is unclear

A migration phase must leave the system in a supported state. Additive and reversible steps precede cutover; destructive cleanup follows verified zero use.

Artifact Rules

  • Reuse a clear architecture migration document; otherwise use docs/architecture/migration-plan.md.
  • Treat current-state, target-design, baseline, decisions, diagrams, interfaces, and telemetry as optional shared evidence.
  • Keep the plan architectural: phases, compatibility, data, topology, gates, rollback, ownership, and removal.
  • Leave file-level implementation tasks to downstream planning.
  • Never describe rollback as "revert" when data or external effects are not reversible.
  • Give every destructive step explicit approval, backup, restoration, and zero-consumer evidence requirements.

Checklist

1. Establish the Transition Contract

  • Resolve migration scope, business outcome, current state, target state, non-goals, deadline or horizon, owners, and approved destination.
  • Read repository instructions, Git state, relevant architecture artifacts, migrations, deployment configuration, and compatibility policies.
  • Verify that current and target states are specific enough to compute a gap; return BLOCKED rather than invent either state.
  • Identify protected user journeys, invariants, SLOs, recovery objectives, compliance duties, and change windows.
  • Keep the run read-only except for the approved migration document.

2. Build the Gap and Dependency Map

  • Inventory affected modules, deployables, data stores, schemas, APIs, events, configuration, infrastructure, and operational procedures.
  • Inventory internal and external consumers, owners, versions, traffic, data volume, and evidence quality.
  • Map current-to-target changes in boundaries, ownership, contracts, data, runtime topology, observability, and failure behavior.
  • Identify shared mutable resources, sequencing dependencies, long-running work, mixed-version windows, and irreversible effects.
  • Record unknown consumers or usage as migration risks; absence of search results is not zero usage.

3. Design Compatibility and Data Safety

  • Define old/new contract compatibility, version negotiation, adapters, dual-read or dual-write behavior, and deprecation policy where relevant.
  • Use expand/migrate/contract when mixed versions or online migration require coexistence; separate additive and destructive releases in that case. For an approved offline atomic transition, document the equivalent compatibility, recovery, and downtime controls.
  • Define backfill selection, batching, throttling, idempotency, checkpoints, retries, reconciliation, and correctness oracle.
  • Define source of truth during coexistence, concurrent-write conflict handling, and detection, retry, and reconciliation of partial dual-write failure; do not assume two writes are atomic.
  • Define backup, restore, RPO/RTO impact, privacy, retention, and audit evi
阅读完整来源 ↗