メニュー
Decide whether to pay down a specific tech-debt by sizing its carrying cost and payback against the roadmap — not all-or-nothing. Reach for this before a 'we must stop and refactor' or 'we never have time' reflex.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill decide-tech-debtコマンドは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 | decide-tech-debt |
| description | Decide whether to pay down a specific tech-debt by sizing its carrying cost and payback against the roadmap — not all-or-nothing. Reach for this before a 'we must stop and refactor' or 'we never have time' reflex. |
Tech-debt is a business decision with a carrying cost, not a moral failing (§3 #7).
Lead-time drift, change-fail, rework, and hotspots — separate felt pain from measured pain (§3 #4 #7). "The codebase is bad" is not a finding.
High churn × high complexity is where paydown has leverage. Stable code, even ugly, is low priority (§3 #7).
Run engineering_management_calc.py tech-debt to compute the carrying cost per period and the payback periods of paying it down (§3 #7).
Pay down when payback is short relative to the code's remaining life; prefer incremental (strangler-fig) over a rewrite (the highest-risk, longest-payback option). Reserve a standing capacity slice rather than a one-off crusade.
A tech-debt decision memo: measured pain, hotspot status, sized carrying cost + payback, and a recommendation with a capacity slice. Use ../../templates/tech-debt-decision-memo.md. Traverse Tree 3. The architecture itself routes to ravenclaude-core/architect.