Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →huytieu/ultragoal
Run a large, multi-session goal (e.g. shipping a whole side product) through the full V-model closed loop, one phase at a time, with cross-session state and a final north-star acceptance gate. Ultragoals never downgrade the lane: every phase runs CP-1→CP-6 with adversarial verification. Use via /ultragoal.
Passed 15 of 20 test cases with the skill, and 6 of 20 without it.
and 11 more in the full report
10 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We created spec.md and STATUS.md for our new initiative 'search-v2' under 04-projects/search-v2/. What global harness file must also be updated to track this new goal?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies 04-projects/harness/ultragoals.md as the central registry file. | Missed | Passed |
The instructions your model reads when the skill loads.
An ultragoal is the term for a north-star that spans many sessions: fork the repos, combine the strong parts, ship one product. A normal /execute run is one task through the loop. An ultragoal is a chain of phases, each of which is its own full closed-loop run, tracked so any cold session can resume.
Core rule (from dwarves-kit, adopted fully): the worker never grades its own homework, and wrongness compounds across sessions — so verify every phase, not just the end.
/ultragoal <name> — resume or advance an existing ultragoal/ultragoal new "<north-star>" — charter a new one/ultragoal status — report all ultragoals from the registryDo not use for single-run work — that is /execute. Rule of thumb: if it needs a phase decomposition and won't finish today, it is an ultragoal.
| File | Role |
|---|---|
04-projects/harness/ultragoals.md | Registry: every ultragoal, status, current phase |
04-projects/<goal>/spec.md | Contract: north-star + AC-n acceptance criteria + phases P0…Pn + traceability matrix |
04-projects/<goal>/STATUS.md | Living ledger: phase state, current phase, open AC-n, next action (resume from here) |
04-projects/<goal>/evidence/P<n>/ | Per-phase evidence bundle (ledger.md + CP-* files) |
Code, if any, lives outside the vault (e.g. ~/code/<goal>/) — the spec/status/evidence stay in the vault.
/ultragoal new)04-projects/<goal>/spec.md from 04-projects/harness/templates/SPEC-template.md:
AC-n acceptance criteria (these define done for the whole goal)P0…Pn — each phase is a shippable increment mapped to a subset of AC-nAC-n ↔ phase ↔ status)STATUS.md (see template below) and add a row to the registry.Record: bash .claude/lib/checkpoint.sh record 04-projects/<goal>/evidence/P0 CP-1 PASS "N criteria, M phases"
test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.