Claude Code と OpenAI Codex CLI の /goal モードとペアリングする単一ファイルエージェントゴールレジャー。

[/goalモードは、エージェントが1つの耐久性のある目的で指摘したままに素晴らしいです。 既に起きたことを思い出すのは素晴らしいことではありません。 目標 Ledger は、すべてのチェックポイント、決定、ブロッカー、検証が 1 つの人間が読める [implementation-notes.html]] ファイルに書かれ、任意のブラウザで開き、コンパクト化、ハンドオフ、チェーンされた目標を生きます。

同じスキルは、両方のエージェントで動作します。 同じ[SKILL.md、同じスクリプト、同じオンディスクレイアウト。 [~/.claude/skills/goal/と~/.codex/skills/goal/にドロップすると、両方のエージェントがネイティブにピックアップします。

それが何をするか

エージェントが[$goal、/goal mode、[start a goal]、または同等のゴールモード言語、スキルを言うとき:

1。 現在のプロジェクトで.agent/runs/ /の下に新しいレジャーを作成します。 2. 契約ファイル([GOAL.md])を記述する:目的、仕上げの基準、エスケープハッチ、親の目標。 3. 単一の正式な状態ファイル([implementation-notes.html])を記述する: [[Resume Here]]のブロックと埋め込まれた進捗タイムライン。 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.