メニュー
Assess a legacy system and choose a modernization strategy with the 6 R's (retain/rehost/replatform/refactor/rearchitect/replace). Reach for this when the question is 'rewrite or refactor?' or 'is this worth modernizing?'.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill assess-legacy-estateコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Route everyday, well-defined work (single-file edits, test-writing, summarization, mechanical refactors, boilerplate) to a cheaper coding agent (Grok or Copilot CLI) instead of doing it in the main Claude session, escalating multi-file/architecture/debugging/security work to Claude. Opt-in via the `cheap_lane:` comfort-posture knob.
Authors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.
Drafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.
| name | assess-legacy-estate |
| description | Assess a legacy system and choose a modernization strategy with the 6 R's (retain/rehost/replatform/refactor/rearchitect/replace). Reach for this when the question is 'rewrite or refactor?' or 'is this worth modernizing?'. |
Decide whether and how to modernize before any code changes.
List what the system does, its dependencies, runtime, data stores, and the team that owns it. Cite the pain it causes (incident load, lead time, change-failure rate) — don't assert it (§2 #7).
The specific reason to change this now: scaling limit, change-failure rate, security/end-of-life, hiring drag, cost, or strategic pivot. No driver → retain.
Traverse the 6-R's tree in ../../knowledge/legacy-modernization-decision-trees.md. Most estates are a portfolio of R's, decided capability by capability — not one verdict for the whole system.
Quantify the cost of not modernizing vs the cost/risk of doing it. Recommend only when the trade is favorable. Date and source every external figure.
Order the work so increments ship early, the riskiest unknowns de-risk first, and rollback stays cheap. Capture it in the modernization-assessment template.