codex-goal-loop

Automate creation and management of Codex goal loops with lifecycle controls.

61|11|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/Matymatyk-business/david-skills --skill codex-goal-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-goal-loop
Source: https://github.com/Matymatyk-business/david-skills/tree/main/skills/codex-goal-loop
Command: npx skills add https://github.com/Matymatyk-business/david-skills --skill codex-goal-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex /goal loops provide a structured, contract-driven approach to running persistent agent workflows, turning vague automation prompts into verifiable, stop-condition-guided executions.

Core Features & Use Cases

  • 4-part contract: Objective, Constraints, Validation, Stop Condition to govern long-running tasks.
  • Lifecycle states: pursuing, paused, achieved, unmet, budget-limited to manage progress.
  • Launch & control: easy startup in a working directory and commands to pause, resume, or clear goals.
  • Use cases: long-running migrations, feature benches, or codebase refactors that require multi-step automation with checkpoints.

Quick Start

Configure Codex in your project workspace and issue a /goal contract outlining the objective, constraints, validation, and stop condition.

Frequently Asked Questions about codex-goal-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a Codex goal loop and how does it manage autonomous agent workflows?▼

A Codex goal loop is a contract-driven workflow that automates persistent autonomous agents using plan-act-test-review iterations. It governs long-running tasks through a 4-part contract and lifecycle states, turning vague prompts into verifiable executions with clear stop conditions.

How do I set up and start a persistent goal loop for a long-running codebase refactor?▼

To start a persistent goal loop, configure Codex in your working directory and issue a /goal contract. You must define the objective, constraints, validation criteria, and stop condition to govern the autonomous agent's multi-step refactoring automation.

Can I pause and resume an autonomous agent during a complex software migration?▼

Yes, you can pause and resume autonomous agents during complex migrations. The skill tracks lifecycle states including pursuing, paused, achieved, unmet, and budget-limited, allowing you to apply start and stop controls to manage checkpoints.

What components make up the 4-part contract for governing persistent agent workflows?▼

The 4-part contract consists of an objective, constraints, validation, and a stop condition. These components work together to govern long-running agent workflows, ensuring persistent executions remain verifiable and stop-condition-guided across software environments.

When should I use a contract-driven goal loop instead of a standard automation prompt?▼

Use a contract-driven goal loop for long-running migrations, feature benches, or codebase refactors requiring multi-step automation with checkpoints. Standard automation prompts lack the lifecycle states and 4-part contracts needed to manage verifiable, persistent agent executions.

What are the limitations of using lifecycle states for autonomous agent workflows?▼

Lifecycle states track progress as pursuing, paused, achieved, unmet, or budget-limited, but the approach requires defining strict validation and stop conditions. Without clear multi-step checkpoints, complex projects may hit budget limitations before the objective is achieved.