메뉴
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명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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.