Spec Goals
Use when someone asks 'help me write a /goal', 'turn this into a goal', 'draft a goal for Codex', 'spec this for /goal', 'is this a good goal', or 'sharpen this objective'. Turns a defined, durable objective into a ready-to-paste Codex `/goal` with a measurable outcome, verification surface, constraints, boundaries, iteration policy, and blocked-stop condition. If the outcome, evidence, constraints, or approach still contains load-bearing unknowns, use flex-finding-unknowns first. Do NOT use this skill to execute the work.
Install
npx skills add sidneyswift/skills --skill spec-goalsgit clone --depth 1 https://github.com/sidneyswift/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/spec-goals ~/.claude/skills/spec-goalsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# spec-goals — turn a vague idea into a strong Codex `/goal`
A Codex **Goal** is a persistent objective attached to a thread: Codex keeps working toward it across turns, deciding the next action on its own, and only marks it done when **evidence** proves it. A vague prompt ("make it faster," "reproduce this paper") wastes that power because Codex has no finish line to check against.
This skill turns a Goal-shaped task into a `/goal` that is **narrow enough to audit but broad enough for Codex to discover the path.** If the task's outcome, evidence, constraints, or approach still contains load-bearing unknowns, use **flex-finding-unknowns** before drafting the Goal. You produce the text; the user pastes it into Codex.
> Command note: the feature is called **Goals**, but the actual command is singular — `/goal`. Goals require Codex `0.128.0` or newer.
## Step 1 — Check the task is Goal-shaped (do this first, every time)
A Goal is the right tool **only when all three are true**:
1. **Durable objective** — there's one outcome worth holding across many turns.
2. **Evidence-based finish line** — something concrete can prove it's done (a test, a benchmark, a build, a report, command output, an artifact).
3. **Uncertain, multi-turn path** — the next step depends on what Codex learns along the way.
If any of those is missing, **say so and recommend a normal prompt instead** — do not force a Goal.Details
- Skill name
spec-goals- Repository
- sidneyswift/skills
- Path
spec-goals/SKILL.md- Repo updated
- 9 November 2026
FAQ
What does the Spec Goals skill do?
Use when someone asks 'help me write a /goal', 'turn this into a goal', 'draft a goal for Codex', 'spec this for /goal', 'is this a good goal', or 'sharpen this objective'. Turns a defined, durable objective into a ready-to-paste Codex `/goal` with a measurable outcome, verification surface, constraints, boundaries, iteration policy, and blocked-stop condition. If the outcome, evidence, constraints, or approach still contains load-bearing unknowns, use flex-finding-unknowns first. Do NOT use this skill to execute the work.
How do I install the Spec Goals skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sidneyswift/skills --skill spec-goals. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spec Goals popular?
It lives in sidneyswift/skills, which has 9 GitHub stars and 1 forks.
Related skills
Design Inspiration
9sidneyswift/skills
Break through design blocks by systematically mining curated inspiration sources. When you're stuck on UI, brand, layout, or visual direction, this skill walks you through nine high-signal design galleries — each covering a different design surface — to find patterns, steal structure, and restart your creative momentum. Use when someone is stuck, needs visual references, wants to explore design directions, or asks "what should this look like?
Design Visual Experiences
9sidneyswift/skills
Create or refine original digital visual experiences where art direction, motion, interaction, or spatial behavior is central. Use for expressive interfaces, interactive explainers, creative coding, and visual films; translate relevant references into implementation decisions and inspect the delivered result.
Ecosystem Mapping
9sidneyswift/skills
Take a core solution or transformation and map every friction point around it into a compounding product ecosystem — instead of building standalone products. Walks the user through identifying their core transformation, mapping friction points (before, during, after), spotting two-sided market opportunities, and designing products that strengthen each other. Use when someone has a working solution but is stuck on "what's next," wants to expand beyond a single product, or is thinking about leverage and ecosystem strategy.
Vscode Ready
9kargnas/skills
Use only when the user asks to set up VS Code/Cursor launch, debug, run, or tasks configs (e.g. "make this project VSCode-ready"). Do not run on your own.
Finding Unknowns
9sidneyswift/skills
Surface the gaps between what a task description says and what the work actually requires, before writing code. Use before implementing anything ambiguous, large, or unfamiliar; when the user asks "what am I missing", wants options or design directions, needs a mock or plan to react to, wants to be interviewed about a spec, is porting from a reference implementation, or gives a vague creative request they lack vocabulary for. Make sure to use this skill whenever the map (prompt/spec) might not match the territory (codebase/real requirements) — even if the user does not say "unknowns.
Ziniao Access Policy
9ziniao-open/skills
紫鸟访问策略管理:网页访问规则、网页/网页分组、规则生效成员/账号、账号绑定策略的查询和维护。当前无快捷命令,全部通过 ziniao-cli api 直调。
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.