SkillAgentSearch skills...

ln-26-architecture-migration-planner

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

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of ln-26-architecture-migration-planner

ln-26-architecture-migration-planner scores 82/100 on our quality scale, 970th of 1,148 Content & Media skills we index.

Its SKILL.md is 12 KB long, well organised into 13 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 566 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
13/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so ln-26-architecture-migration-planner is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-15. Automated pattern scan on 2026-10-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ln-26-architecture-migration-planner compared with similar skills

All 4 of these similar skills score higher than ln-26-architecture-migration-planner; compare them before choosing.

SkillScoreStarsUpdatedFormat
ln-26-architecture-migration-planner (this skill)by levnikolaevich825662mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
algorithmic-artby anthropics100177.9k57d agoSKILL.md
pptxby anthropics100177.9k57d agoSKILL.md
prospectingby coreyhaines3110060.1k7d agoSKILL.md

Frequently asked questions

How do I install ln-26-architecture-migration-planner?
Run npx skills add levnikolaevich/claude-code-skills --skill ln-26-architecture-migration-planner. The install tabs above show the steps for each supported agent.
Which AI agents does ln-26-architecture-migration-planner work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is ln-26-architecture-migration-planner safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ln-26-architecture-migration-planner still maintained?
The repository was last updated about 2 months ago, so ln-26-architecture-migration-planner is actively maintained.

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: Track every checklist item as PENDING, PROVEN with observed outcome evidence, CLEARED with evidence its condition is absent, or UNPROVEN with a gap. Reading, delegation, tool failure, zero exit status, and self-reported success are not proof. Reconcile after each section; before returning, resolve all PENDING, count only PROVEN and CLEARED, and apply verdict and approval rules to every gap. Preserve intent, scope, mode, and existing authorization. Complete authorized work before required external approval; ask only consequential unresolved choices. If nobody can answer, report the exact question and apply the skill's gap verdict without waiting or guessing. Cite any blocking instruction and unresolved boundary; never invent approval gates. Scale depth to material risk; preserve mandatory checks, dependencies, and safety order while choosing verification methods. Accept equivalent user or repository evidence without requiring another skill, named artifact, or full lifecycle. Preserve source requirement and decision IDs. Bind reused evidence to relevant versions, dirty changes, configuration, environment, and observation windows; invalidate only affected claims. Choose the primary workflow by outcome and explicit selection. Consume neighboring contracts and valid evidence without duplicating ownership or restarting audits. Split distinct deliverables by scope, not mandatory skill invocation. Broad independent assessments use audit workflows; focused domain reviews remain read-only. On continuation, reconcile task, authorization, state, and gaps. Return a compact continuation record for long work or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority. Before retrieval, define the evidence question; read selectively without skipping applicable instructions. Use tools for mechanical processing; summarize bounded results, errors, coverage, and source paths, keeping full output outside context. Before technical decisions, establish applicability and actual versions; verify version-dependent assumptions against official documentation or specifications. Search and read primary pages for current external recommendations; snippets are not evidence. Version-matched bundled documentation or valid prior evidence suffices. Record decision, version, source, and limitations. Mark unavailable evidence UNVERIFIED; block only essential dependent work. Prefer native mechanisms, justify added tools or abstractions with evidence, and reuse the existing rule owner.

Tool Routing

| Need | Preferred capability | Fallback | |---|---|---| | Current and target states | Repository evidence plus approved architecture artifacts | Explicit user-provided states with limitations | | Consumers and compatibility | Language intelligence, schema tools, config search, telemetry, and direct inspection | Conservative inventory marked UNVERIFIED | | Data scale and runtime risk | Production metrics, checked-in reports, migrations, and workload evidence | Ranges with validation gates before execution | | External migration constraints | Official vendor migration and compatibility guidance | Mark dependent phases BLOCKED or UNVERIFIED | | Document mutation | Minimal patch to the approved migration-plan artifact | Return 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.

Workflow Boundary

This workflow owns the architecture transition plan and compatibility sequence, not migration execution. Database lifecycle changes consume that sequence without redefining its business or architectural commitments.

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 evidence for data movement.

4. Build Reversible Phases

  • [ ] Choose the fewest applicable, independently verifiable phases from preparation, shadow or coexistence, progressive migration, cutover, stabilization, and old-path removal. Do not force shadow or progressive migration for an approved offline atomic transition; preserve applicable compatibility, recovery, irreversible-action, and entry/exit evidence requirements.
  • [ ] For every phase, state prerequisites, changed architecture state, owner, entry gate, observable success, abort condition, rollback or roll-forward action, and exit evidence.
  • [ ] Define feature flags, routing controls, canary cohorts, rate limits, maintenance windows, and blast-radius controls where justified.
  • [ ] Define metrics, logs, traces, reconciliation reports, dashboards, alerts, and SLO gates needed before traffic or data movement.
  • [ ] Keep old and new versions interoperable through realistic deployment ordering and rollback windows.

5. Plan Cutover and Removal

  • [ ] Define go/no-go authority, communication, freeze conditions, exact cutover control, and immediate verification.
  • [ ] Define rollback boundaries separately for code, configuration, traffic, schema, and migrated data, including points of no return and roll-forward recovery when rollback would lose accepted writes.
  • [ ] Before destructive removal, require usage evidence over a window covering relevant schedules and offline consumers, migrated consumers, applicable retention expiry, and explicit approval. A short zero-traffic sample cannot establish zero use.
  • [ ] List old code paths, contracts, flags, adapters, jobs, data, infrastructure, dashboards, and documentation to remove.
  • [ ] Define post-cutover observation period, ownership handoff, incident response, and closure evidence.

6. Write and Report

  • [ ] Write transition summary, state gap, dependencies, compatibility, data plan, phased sequence, gates, observability, rollback, removal, owners, assumptions, and open decisions.
  • [ ] Link shared artifacts by stable repository path or title without requiring a particular workflow.
  • [ ] Re-read every phase for unsupported zero-downtime, zero-loss, consumer, capacity, or reversibility claims.
  • [ ] Link each transition unit to the protected requirement, current/target boundary, entry evidence, observed success, and irreversible point; identify dependent plans affected by a migration change.
  • [ ] Apply the verdict to the plan artifact: READY only when no unresolved decision changes planned data semantics, compatibility, phase order, or recovery; INCOMPLETE for a useful plan with any such decision or missing gate/rollback rule. Assigning an owner or deferring a decision to a phase gate does not resolve it. Use BLOCKED only when scope, authority, essential current/target evidence, or safe document creation cannot be established. Pending live verification alone is an execution prerequisite, not a reason to block a useful plan.

Self-Check

  • [ ] Reconcile before returning. Check item-level evidence, requirement coverage, contradictions, scope, verdict, and applicable cleanup. Correct the report or authorized artifacts. Reuse valid evidence; do not automatically rescan the repository or rerun successful commands. Repeat checks only for relevant changes, failures, or unresolved evidence. Disclose remaining gaps.

Output Contract

Report in the user's language, in this order; label all five fields and state each fact once. Use controlled plain language: one fact per sentence, usually under 20 words, active voice, and one term per concept, with no synonyms for verdicts, IDs, or states. Small results may use one line per field; omit empty tables and do not copy linked artifacts:

  1. Result: The exact skill-specific verdict token first, then the supported outcome.
  2. Scope: Reviewed/changed scope, exclusions, baseline, and material assumptions.
  3. Evidence: Skill-specific fields below; distinguish facts, inferences, and unverified claims. Link artifacts; use tables when useful.
  4. Verification: Checks/results, unavailable evidence, and applicable cleanup/external state.
  5. Completion: Checklist: X/Y complete; Incomplete: None or each UNPROVEN item's reason, outcome impact, and exact next action; residual risks and required decisions.

Skill-specific evidence: Artifact path; current/target gap, consumers, dependencies, and protected invariants. Summarize phases with entry gates, changes, success evidence, abort conditions, rollback/roll-forward; data/coexistence/reconciliation/cutover/removal proof; and open decisions that affect safety, ordering, or reversibility. When there are more than a few phases and the host renders Markdown diagrams, add one Mermaid phase-and-gate diagram; keep the text

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars566
CategoryContent
Updated2mo ago
Forks84

Languages

PowerShell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions