# Vault Revamp Katman

> How to complete a kanban-driven Unreal Engine/Obsidian vault revamp task safely and unitarily across the category notes.

- Skill: `theheavenlyd3mon/vault-revamp-katman` (Agent Skill)
- Install (CLI): `npx skillmds add theheavenlyd3mon/vault-revamp-katman`
- Raw SKILL.md: https://api.skillmd.com/api/skills/theheavenlyd3mon/vault-revamp-katman/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: theheavenlyd3mon (https://skillmd.com/u/theheavenlyd3mon)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/theheavenlyd3mon/vault-revamp-katman

---


# Vault Revamp (kanban worker)

## Orientation

Always read `kanban_show()` first. For a revamp task, the two trustworthy inputs are:
- `_UE5_8_Convention_Standard.md`
- `Research/_incoming/curation_report.md section 2` for your category

## Work discipline

- Do not modify files outside the task workspace unless the body explicitly requires it.
- If saving every request costs a turn, limit automation to once after all category notes are annotated.
- Cease editing the next note only after successful completion of the active one.

## Classification choice

- Prefer `status: current` with `historical_notes` when no deprecated symbols are present.
- Use `status: legacy` / `deprecated` only when the standard or curation report explicitly identifies removed/deprecated APIs.
- Do not guess deprecated artifacts from memory.

---
