Find My Goal

find-my-goal

**If you can type, you can use /goal.** · [中文说明](README.zh-CN.md)

❌ /goal optimize my project
   → no criteria, no budget, no brake: the loop wanders, burns tokens, stalls halfway

✅ /goal Goal: cut full npm test time from baseline 84s to under 40s, all green
        Scope: only src/ and tests; no public API changes, no new deps
        Done when: npm test exit 0; 3 consecutive runs each ≤ 40s
        Stop if: needs new deps; same idea fails 3 times
        Budget: max 15 iterations
   → runs until the evidence says done

You don't learn to write the right-hand side — find-my-goal writes it for you. Say it in plain words, answer a few multiple-choice questions, paste the draft into `/goal`. Works in English or Chinese.

[](LICENSE) [](find-my-goal/SKILL.md)

TL;DR

# Install (one-time, pick one)
npx skills add Kaiji-Z/find-my-goal                                   # any agent (skills.sh CLI)
git clone https://github.com/Kaiji-Z/find-my-goal ~/.claude/skills/   # Claude Code
git clone https://github.com/Kaiji-Z/find-my-goal ~/.agents/skills/   # ZCode / cross-tool

# Use (in any session, plain language)
Help me write a goal: make our mini-app start faster

How it works

you speak plainly ──► at most 3 multiple-choice questions (every one has a "you decide" option)
──► a baseline run for real numbers ──► a five-part strong goal (awaits your confirmation)
──► paste into /goal

The five parts = Goal / Scope / Done-when / Stop-if / Budget. Criteria must be an executable command + expected exit code or threshold — "feels done" doesn't count. That is the entire secret of stopping /goal from spinning.

Why this exists

ZCode, Codex (0.128+) and opencode-with-omo all have `/goal` — a kernel-level persistent goal loop that auto-continues until the goal is verifiably done. Great, except:

/goal