메뉴
Use to harvest `debt:` markers across the repo into a debt ledger and optionally persist it to the Obsidian vault. Triggers on "부채", "기술부채", "debt", "지름길 정리", "/debt". Read-only — does not modify code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | debt |
| description | Use to harvest `debt:` markers across the repo into a debt ledger and optionally persist it to the Obsidian vault. Triggers on "부채", "기술부채", "debt", "지름길 정리", "/debt". Read-only — does not modify code. |
Harvest the # debt: / // debt: markers that executor leaves for intentional simplifications, and turn them into a ledger. Read and report only — never modify code. One-shot.
Identify project — run scripts/identify-project.sh to resolve PROJECT.
Grep the repo for debt markers (exclude node_modules, .git, and build artifacts):
grep -rnE '(#|//) ?debt:' . --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist --exclude-dir=build
You may delegate this grep to the explore agent (quick category).
Build the ledger, one line per marker, grouped by file:
<file>:<line>, <what was simplified>. ceiling: <stated limitation>. upgrade: <re-review trigger>.
For markers without a stated limitation or trigger, tag them no-trigger (silent-rot risk).
Summarize at the end:
<N> markers, <M> with no trigger.No debt markers. Clean ledger.Persist only on request. Output the ledger to the user. If the user asks to persist it, delegate to the archivist agent (haiku) to save it to vault {PROJECT}/debt-ledger.md using scripts/vault-save.sh (or scripts/vault-update.sh to append). Never auto-save.
Honesty boundary. Never emit fabricated savings figures like "saved N lines in this repo" — code that was never written has no baseline. The only real numbers are the counts in the ledger.
After presenting the ledger, scan each marker's upgrade: trigger. If any trigger now appears met (e.g. the named threshold is likely crossed, or the user says they want to act on it), offer — do not auto-run — to resolve the selected items:
"다음 항목들의 트리거가 충족된 것으로 보입니다: [목록]. 이 중 처리할 항목을
agmo:plan으로 넘길까요?"
On explicit user confirmation, hand the chosen ledger rows to agmo:plan (each row's file:line + ceiling + upgrade trigger becomes the design input); the normal plan → execute pipeline does the actual fixing. For a single trivial row, the user may instead route straight to the executor agent.
This handoff is a routing offer only — this skill still never modifies code itself. Surfacing debt and resolving it stay separate steps; the skill only connects them when the user opts in.
agmo:plan, it never edits code in this skill.debt: convention documented in agents/executor.md.Loaded automatically at session start. Teaches the orchestrator how to route requests to skills and agents. Do not invoke manually.
Use when the user wants to explore an idea, design an approach, or think through a problem before implementing. Triggers on "고민", "논의", "아이디어", "brs".
Use when code review is needed. Triggers on "코드 리뷰", "리뷰해줘", "code review", or at completion of implementation.
Use when the user wants to run an implementation plan. Triggers on "실행해줘", "구현해줘", "시작해줘", "execute", or after plan approval.
Implement an entire Figma page as Android Jetpack Compose screens by auto-splitting into frames with visual verification. Use whenever a user shares a figma.com/design URL and wants the page built as Compose code. Triggers on '안드로이드 피그마', 'Android Figma', 'Compose 구현'. Covers any multi-frame page. Does NOT apply to Figma asset downloads or single component edits.
Implement an entire Figma page by auto-splitting into frames with visual verification. Use whenever a user shares a figma.com/design URL and wants the page built in code. Triggers on '피그마 구현', '피그마 페이지', 'Figma implement'. Covers any multi-frame page: landing, dashboard, marketing, etc. Does NOT apply to Figma asset downloads or single component edits.