chrischabot

Claude Code Goal — Documentation skill for Claude Code

Documentation community

Persistent markdown-backed goal mode for Claude Code.

How to install Claude Code Goal

This entry records only its repository, not the path inside it, so there is no exact command to give. Open chrischabot/claude-code-goal and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Goal does

Persistent markdown-backed goal mode for Claude Code.

Alternatives in Documentation

  • 会话管理(Session Manager)需求文档(PRD / Markdown) — 目标:对 Codex / Claude Code 的本地会话记录进行可视化管理,并提供“一键复制 / 一键终端恢复”能力 31.7k ★
  • Repo Recap — Generate a structured recap of the repository state: open PRs, open issues, recent releases, and executive sum 11.9k ★
  • Ars Format Convert — ARS academic-paper format-convert mode — convert to LaTeX / DOCX / PDF / Markdown 4.5k ★

README

Claude Code Goal Plugin

Persistent, markdown-backed goal mode for Claude Code.

This plugin adds a `/goal:*` command family and lifecycle hooks that keep Claude working on an active objective until the objective is genuinely complete or a configured iteration ceiling is reached.

It is inspired by two existing systems:

  • Codex /goal, which treats a long-running user objective as durable state rather than as a single prompt.
  • Claude Code Ralph loops, which demonstrate that a Stop hook can block turn termination and feed Claude a continuation prompt.

The goal here is not to clone either system perfectly. It is to bring the useful behavior to Claude Code using the extension surfaces Claude Code actually supports today: plugins, slash commands, hooks, and local files.

Quick Start

Install from this marketplace repo:

claude plugin marketplace add chrischabot/claude-code-goal
claude plugin install goal@claude-code-goal

Restart Claude Code after installing. Then run:

/goal:goal Fix the parser bug, add a regression test, and run the targeted test command --max-iterations 8 --completion-promise GOAL_COMPLETE

Claude should continue working until it can truthfully output:

GOAL_COMPLETE

Check status at any point:

/goal:status

Why This Exists

Large coding tasks rarely fit cleanly into a single assistant turn. A normal Claude Code session tends to stop once it has produced a reasonable-looking answer, even when there is still more verification, cleanup, or follow-through to do.

Codex `/goal` addresses this by making the task itself a durable runtime concept. The user creates a goal, the agent keeps state about it, and the runtime can keep nudging the agent forward until the goal has actually been satisfied.

Claude Code does not expose Codex's internal goal runtime. It does, however, expose enough extension points to approximate the important behavior:

  • Slash commands can create and muta