Turn plain-English goals into tracked, evidence-driven workflow phases with status diagrams, plain-language decisions, retrospectives, and regression-aware improvement suggestions for Claude Code and Codex.
Render a clean diagram of the goal's architecture or loop.
Show the active goal's status, proof, and what needs the user.
Start a new Goals-managed goal and begin its first phase.
Retrospective on a completed or stalled Goals goal — learn from it and optionally file engine friction upstream.
Import an external loop definition or catalog into Goals.
Generate a clean architecture or loop diagram for the active Goals goal as Mermaid or a valid .excalidraw file. Use when the user asks to visualize, diagram, or draw the goal's architecture map or the designed loop.
Show the architecture map of the active Goals goal — what is built, planned, blocked, deferred, or missing. Use inside a Goals project when you need the system shape, a diagram-style overview, or to check recorded changes against the goal's architecture.
Run a retrospective on a completed (or stalled) Goals goal to learn from it — critique both the engine/UX friction the CLI created AND the agent's own execution quality, record durable lessons into self-evolution memory, surface cross-goal patterns, and file engine friction upstream. Use after `goals check` reports a goal complete, after a painful or stalled goal, or periodically to learn across every goal you run.
Explain a project decision from the active Goals goal in plain language — what needs the user, the recommended reply, and what happens next. Use inside a Goals project when a technical decision, risk, or tradeoff needs a non-technical explanation, or when deciding whether a choice should interrupt the user.
Solve a problem or define/break down a goal using PACERS (Pause, Assess, Choose, Execute, Review, Systemize) and record the reasoning as a traceable building journey in the active Goals goal. Use inside a Goals project when defining a goal, breaking a phase into sub-problems, hunting assumptions before building, or whenever a problem is recurring, costly, unclear, or likely to create second-order effects.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Goals is an open-source plugin for Claude Code and Codex that helps an AI agent run long enough to actually finish your goal.
It builds on the native /goal loop instead of replacing it: the agent still does
the work, while Goals adds the durable plan, the proof each step ran, the
decisions, and a memory of how you like things done — the things a long run needs
to be something you can trust, check, and pick back up. Everything it does lives
in plain files you own.

Just say what you want — for example:
Anyone using AI to get real work done:
you say the goal
│
▼
Goals breaks it into clear steps ──▶ the AI agent does the next step
▲ │
│ you say yes ◀──── plain decision + proof it works
└───────── repeat until done — with a record of everything ◀─┘
Goals runs the workflow; your AI assistant (Claude Code, Codex, …) does the work. Goals is the part that keeps it organized, legible, and accountable.
Under the hood it's a small CLI plus a plugin, working over plain files in
your own project — so the goal, the decisions, and the proof are yours and
survive a /clear or a brand-new session. The assess step follows PACERS, a
method for solving problems without rushing.
Here's the whole loop, each step in plain English (click to enlarge):
And you never lose the thread: a dashboard anyone can read shows status, decisions, and proof at a glance (click to view full size):
Diagram source: docs/assets/lifecycle.mmd — regenerate with npx -y @mermaid-js/mermaid-cli -i docs/assets/lifecycle.mmd -o docs/assets/lifecycle.png -b white -s 2.
See docs/architecture.md for the full set: system
architecture, the goal lifecycle, skill-first discovery + capability gaps, and the
portability layer that lets a goal survive /clear.
Two lines — that's the whole install:
/plugin marketplace add ShivamGupta42/goals
/plugin install goals@goals
npx claudepluginhub shivamgupta42/goals --plugin goalsTurn broad Codex and Claude Code work into pressured /goal runs with oracles, local boards, receipts, and verification.
Plan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry, fix-spec recovery, and per-phase memory writeback. Works on Claude Code and Codex.
Durable goal-following for Claude Code: contracts with definition-of-done, subagent judge gates, executor-subagent chain execution, and adaptive missions. Inspired by OpenAI Codex /goal and the Ralph loop pattern.
Zero-config goal-to-tasks engine for Claude Code (the Atlas engine). Graded PRD validation, dependency-ordered task graph, and CDD-verified execution.
Tell Claude what you want once; it works until the job is verifiably done, then saves what it learned. Goals with checkable specs, independent verification, and a memory that grows.
A structured goal-setting exercise grounded in MCII research to help developers set concrete learning goals with if-then plans for follow-through.