[/goal]] 모드가 Claude Code 및 OpenAI Codex CLI로 쌍하는 Single-file Agent 목표 ledger.

/goal 모드는 1개의 튼튼한 목표에 있는 대리인을 지키기에 중대합니다. 이미 일어난 것을 기억하는 것은 좋지 않습니다. Goal Ledger는 간격을 채웁니다: 모든 검문소, 결정, 차단제, 그리고 검증은 어떤 브라우저에서 열리고 조밀하고, 손 떨어져 살아남는, 그리고 사슬로 만들어진 목표에 있는 1개의 인간 읽기 쉬운 [T2]] 파일로 썼습니다.

동일한 기술은 두 대리인에서 작동합니다. 같은 SKILL.md, 같은 스크립트, 같은 on-disk 레이아웃. ~/.claude/skills/goal/]와 ~/.codex/skills/goal/]으로 떨어뜨리며, 두 에이전트는 기본적으로 선택합니다.

무엇 그것

에이전트가 $goal, /goal mode], start a goal], 또는 어떤 동등한 목표 모드 언어, 기술:

1. 현재 프로젝트에서 .agent/runs/ /] 아래 신선한 ledger를 만듭니다.
2. 계약 파일 (GOAL.md])를 작성: 목적, 마무리 기준, 탈출 해치, 부모 목표.
3. Single Canonical state file (implementation-notes.html])를 작성합니다. Resume Here]] 블록을 상단과 임베디드 진행 타임라인으로 통합된 HTML 페이지입니다.
4. 명세.

Goal Ledger

A single-file agent goal ledger that pairs with /goal mode in Claude Code and OpenAI Codex CLI.

/goal mode is great at keeping an agent pointed at one durable objective. It is not great at remembering what already happened. The Goal Ledger fills that gap: every checkpoint, decision, blocker, and validation gets written into one human-readable implementation-notes.html file that opens in any browser and survives compaction, hand-offs, and chained goals.

The same skill works in both agents. Same SKILL.md, same script, same on-disk layout. Drop it into ~/.claude/skills/goal/ and ~/.codex/skills/goal/ and both agents pick it up natively.

What it does

When the agent says $goal, /goal mode, start a goal, or any equivalent goal-mode language, the skill:

1. Creates a fresh ledger under .agent/runs// in the current project.
2. Writes a contract file (GOAL.md): objective, finishing criteria, escape hatch, parent goal.
3. Writes a single canonical state file (implementation-notes.html): a self-contained HTML page with a Resume Here block at the top and an embedded progress timeline.
4. Couples to the runtime goal: when the user is in Codex /goal mode, the absolute ledger path is dropped into the goal objective so the next agent on the thread knows exactly where to read and write.
5. Updates the HTML at every meaningful checkpoint: validation runs, implementation milestones, blockers, spec-vs-reality conflicts, compaction prep, final hand-off.

The progress timeline is rendered directly from an inline progressEvents array inside the HTML file. There is no separate events.jsonl to keep in sync — the page is its own history. Open the file locally and you get the whole story at a glance.

Why one HTML file

Earlier versions of this skill used a sprawl of PROGRESS.md, HANDOFF.md, events.jsonl, and CODEBASE_STATUS.md. Agents got confused about which file was canonical. Humans got confused about which file to read. State drifted between them.

Goal Ledger collapses all of that into one self-contained HTML file:

• Top is a Resume Here block: status, current phase, blockers, next exact action, last validation, protected paths. Built so the next agent (or human) can resume in under a minute.
• Middle is Decisions Outside The Spec, Changes And Tradeoffs, Validation, Evidence. The execution record.
• Bottom is Progress Timeline. Rendered from an inline events array, no external file dependencies, no fetches against sibling files. Opens cleanly even when you double-click the HTML straight out of the file browser.

The HTML is the contract with the next agent. GOAL.md is the contract with the current agent. That’s the whole system.