# Omd:add Reference

> Reference catalog authoring compatibility gate. Core v2 cutover가 끝나기 전에는 신규 legacy DESIGN.md 쓰기를 차단하고 안전한 재개 조건을 설명한다.

- Skill: `kwakseongjae/omd-add-reference-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add kwakseongjae/omd-add-reference-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kwakseongjae/omd-add-reference-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kwakseongjae (https://skillmd.com/u/kwakseongjae)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kwakseongjae/omd-add-reference-2

---


**Expiry.** This gate is a waiting state, not a policy. It lifts when the
catalog adoption path lands — the T2-2 writer gate, tracked in
`docs/OMD_PLAN_2026-09-02.md` §0 "카탈로그 채택 경로" (today: 없다 — the migrated
bodies sit in `docs/design-md-weight/migrated/` and `web/references/` is still
legacy). Until a graph-backed Core v2 writer exists and every catalog reader
accepts its package, this skill refuses catalog writes — all of them, with no
one-off exception and no plausible fallback.

# omd:add-reference — Core v2 catalog cutover gate

Status: `CORE_V2_CATALOG_WRITE_BLOCKED`.

The historical reference catalog remains a dual-read migration input. It is not
permission to create another legacy file. Do not write or update
`web/references/<id>/DESIGN.md`, frontmatter tokens, generated counts, or mirrors.

On invocation, return the blocker and the proposed reference id/source list
without writing. Authoring may resume only after a graph-backed reference
metadata/evidence schema, deterministic Core projection, migrated registry and
quality readers, legacy dual-read/Core single-write tests, and a dropped-zero
migration gate all pass together.

Never restore a legacy YAML marker, 13/15/16-section output, placeholder
sentinels, or a second authoritative Markdown dialect as a shortcut.