메뉴
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | debt |
| description | Harvest `debt:` markers across the repo into a read-only ledger without modifying code. |
| argument-hint | [optional path, area, or debt focus] |
Use this skill when the user wants to inspect intentional simplification markers such as // debt: or # debt:. It is read-only: report the ledger, do not edit code, and do not resolve debt inside this skill.
rg -n '(#|//) ?debt:' . \
-g '!node_modules/**' \
-g '!.git/**' \
-g '!dist/**' \
-g '!build/**' \
-g '!.agmo/cache/**' \
-g '!**/.pnpm-store/**' \
-g '!**/.yarn/**'
file:line, the stated limitation, and the upgrade: trigger when present.no-trigger.<N> markers, <M> with no trigger. If none are found, report No debt markers. Clean ledger.After presenting the ledger, scan for upgrade: triggers that appear to be met. Offer, but do not auto-run, a handoff:
"These markers may be ready to resolve: [list]. Which rows should I hand to
plan?"
Only after explicit confirmation, route selected rows to plan with their file:line, limitation, and trigger. The normal plan -> execute path handles fixes. This skill still never edits markers or code.
// debt: <limitation>, upgrade: <trigger> or # debt: <limitation>, upgrade: <trigger>.Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
Use when the user wants a GitHub issue created from the current conversation or repo context. Triggers on requests like "이슈 만들어", "깃허브 이슈", "create issue", or "new issue". If the source artifact is an existing vault note, use `note-to-issue` instead.