goal-prompt-builder skill
A skill that builds a Codex /goal command from a five-section template so a long task does not drift and passes the audit
- 231 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill is instructions and references; it runs nothing and makes no network calls by itself.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/goal-prompt-builderDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill is instructions and references; it runs nothing and makes no network calls by itself.
This is third-party code. Review the repository files before installing.
What it does
The skill turns a fuzzy task description into a paste-ready `/goal` command for Codex CLI 0.128 and newer. The `/goal` command sets a persistent objective with a completion audit, a token budget and a soft stop. The audit builds a requirement checklist from the goal text, and a vague phrase such as fix the tests and clean up the code gives it nothing to build from. The skill walks through six steps and assembles the goal from five sections in order: objective, scope, constraints, done criteria and stop conditions. It detects the project type from files or a repository URL (Node, Python, Swift, Go, Rust, static site), reads `AGENTS.md` and `CLAUDE.md` if present and rates how audit-friendly the goal is before output. Three interaction modes exist: step by step, full description and hybrid. The `references` folder holds defaults per project type, skeletons for seven scenarios (refactor, feature, batch, archaeology, UI audit, gatekeeper, custom) and five worked examples.
Who it is for. Codex CLI users who launch long autonomous tasks through `/goal` and want to phrase goals so that the audit can check them.
Good fit when
- A task to refactor the auth module has to become a goal with scope, constraints and done criteria.
- Codex drifted on a long task and the goal needs rewriting so that it can be checked.
- Before launching you want to rate how audit-friendly the goal is.
- You need a skeleton for a batch job or a UI check from the ready scenarios.
Not a fit when
- You do not use Codex CLI 0.128 or newer: the `/goal` command appeared there.
- The task is short and fits one prompt: a five-section template is overkill.
- You need Codex itself launched: the skill only writes the command and you paste and run it.
Example request
Help me write a `/goal` for refactoring the auth module: detect the project type, read `AGENTS.md` and output a ready command.Limitations
The skill runs nothing by itself. It writes the text of a `/goal` command that you paste and run in Codex CLI. The rule base is derived from the built-in Codex audit and public discussions, so the template needs rechecking as `/goal` behavior changes in new versions. The author claim of unattended work beyond 20 hours refers to `/goal` itself and not to the skill. Install uses a `.skill` archive unpacked into `~/.claude/skills`, and the README targets Claude and Codex while parts of the text are in Chinese. Project type detection is heuristic and can be wrong.
How to disable. Delete the `goal-prompt-builder` folder from `~/.claude/skills` and the downloaded archive `/tmp/goal-prompt-builder.skill`.
FAQ
How do I install the skill?
Download the archive with `curl -L -o /tmp/goal-prompt-builder.skill https://github.com/win4r/goal-prompt-builder/raw/main/goal-prompt-builder.skill` and unpack with `unzip -o /tmp/goal-prompt-builder.skill -d ~/.claude/skills/`.
What does the goal template consist of?
Five sections: objective, scope, constraints, done criteria and stop conditions.
Which project types does the skill detect?
Node, Python, Swift, Go, Rust and static sites, from project files or a repository URL.
Which scenarios have skeletons?
Refactor, feature, batch, archaeology, UI audit, gatekeeper and custom.
How do I invoke the skill?
Ask for example help me write a /goal for refactoring the auth module. The skill triggers on that request and runs through six steps.
Discussion
No questions or reviews yet.
Related
SkillsA meta-skill for Codex: a vague task becomes a ready "/goal" command with verification, boundaries and pause conditions.
A catalogue of over 300 ready /goal contracts for Claude Code, Codex and Cursor plus a skill that writes such contracts.
A skill that turns a vague request into a Goal Prompt with success criteria and stop conditions, plus a Loop Prompt if needed.
A Codex plugin of five independent meta-skills and one tldraw skill: improves prompts, goals, research, plans and commits.
Skill setting up Markdown file memory for Codex via AGENTS.md: profile, rules, lessons, errors and capability requests.
CodexPotter loops Codex with a clean context each round until the code matches the goal, as a replacement for the built-in /goal.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| goal-prompt-builder (this card) | no | 231 | |
| Goal Workflow | no | 300 | goal-workflow runs a workflow around a goal, while goal-prompt-builder writes the `/goal` command itself from a five-section template. |
| qiaomu-goal-meta-skill | no | 910 | qiaomu-goal-meta-skill works with goals at a meta level, while here there are project type detection, an audit-fitness rating and scenario skeletons. |
README in short
The README explains the `/goal` weak spot with vague goals, the contents of the `.skill` bundle, the sources of the rules and an install example. MIT license, with a Chinese version.