kortix-goals
Work a goal until an independent verifier passes every done criterion, across days or weeks: the Goals API holds the state, the goal folder in Files (`GOAL.md` brief, `log.md`, `evidence/`) holds the
SKILL.mdpackages/starter/templates/managed/skills/kortix-goals/SKILL.md
GitHub<skill name="kortix-goals">
<overview>
A goal is what a person wants plus a definition of done. An owner session
works it. A separate verifier session decides whether it is done.
The Goals API is the authority. It holds the state, pause, stop, owner,
verifier, criteria, caps and counters. It knows which session calls from the
session's own credential: no flag or file can make you the owner, the
verifier or a person. kortix goals calls the API; every refusal it prints
is the API's or the CLI's rule, with the reason.
The folder in Files (/drives/me/Goals/<slug>/ in a session) holds the work:
| File | Holds | Who writes |
|---|---|---|
GOAL.md |
the brief: the person's request, ## Done criteria, context, plan |
you (criteria only while the goal is a draft) |
log.md |
append-only: each wake, what changed, what is next | you; never rewrite earlier lines |
evidence/ |
proof per criterion; verification.md is the verifier's report |
you; the verifier writes verification.md |
After each accepted write the CLI puts a kortix-lifecycle block in GOAL.md's
front matter (state, revision, owner). It is a read-only copy for you. Editing
it, or writing state:, paused_at: or caps into GOAL.md, changes nothing.
kortix goals status is the truth.
</overview>
You cannot reach done, and you cannot stop, pause, resume or restart a goal,
or raise its caps. A person does those from the Goals page.
</lifecycle>
Add --json for machine-readable output and --goal <goal_id> when the CLI
cannot tell which goal you mean. kortix goals new is for a person: in a
session the API refuses it.
</commands>
kortix goals status. Read GOAL.md andlog.md.- Keep the person's done criteria. When there are none, write 1 to 8 under
## Done criteria, each one checkable by someone else and naming its proof. - Write the context: their words, the constraints, the obvious ones (no spend above what they named, nothing irreversible without asking).
kortix goals transition active --reason "criteria written".- Act on the first step in this turn. Append it to
log.md.
A person asks for a goal in chat. You cannot create it. Agree the outcome and the done criteria with them, then ask them to create it from the Goals page. The API starts an owner session for it. </start>
<wake> Every turn on a goal is one wake: the heartbeat, an answer, a verdict, a merged change request, a person in this chat.- Orient.
kortix goals status, GOAL.md, the last 40 lines oflog.md. Paused (paused by a person): do no work, end the turn. - Advance. Do the highest-leverage next step. Use workers for parallel or heavy work.
- Report.
kortix goals progresswith what changed. Append one line per action tolog.md. - Ask when only a person can unblock it: see
<waiting>. - Claim done when every criterion is met with evidence:
kortix goals verify. End the turn. The verdict wakes you. - End the turn. After it, kortixd runs
kortix goals check --enforce. It sends[GOAL CHECK]when your goal is still a draft or you reported nothing for 3 wakes (at most 3 messages per 6 hours). Do what it names.
Context nearly full? Write the state of play (done, in flight, next, open
questions, where things are) and kortix goals handover --note "…". Stop
working the goal after that.
</wake>
While the goal waits, the API runs no heartbeat turn. It wakes you when the
assigned user answers from the Goals page (the goal is active again), or
once at --chase-at (60 minutes to 14 days ahead) when you set it. When the
answer reaches you another way (a reply on the channel you asked on), run
kortix goals transition active --reason "<what they answered>" yourself.
</waiting>
kortix goals status: the current criteria and their evidence.- Check each criterion yourself: open the evidence, then check the real thing (the page, the file, the API, the record). An owner's note is not proof.
- Write
evidence/verification.md: one line per criterion,c1 PASS: <why>orc1 FAIL: <what is missing>. The CLI refuses a verdict without it. - Give exactly one result per current criterion, for example
kortix goals verdict --pass c1,c2 --fail c3 --note c3="charged in USD". A missing, duplicate or unknown id is refused; a fail or inconclusive needs a note. All pass: the goal is done. Any other result: it goes back to the owner with your notes. - Do not edit GOAL.md. Do not fix the work.
A session that owned the goal cannot give its verdict: the API refuses it. </verify>
<limits> A person sets the caps on the Goals page; the API enforces them when a wake starts. `kortix goals status` shows them.- heartbeat (default 4h): how often an
activegoal wakes. - wakes per UTC day (default 12): at the cap the goal is
blocked: wake_capuntil the next UTC day. - sessions per goal (default 10, owners and verifiers): at the cap
verifyandhandoverare refused (session_cap). Ask the assigned user to raise it.
Other blocked reasons: credits (a person tops up and resumes),
owner_lost, storage, flag_off, setup. None of them is yours to fix:
say so in log.md and end the turn.
</limits>
When ls prints "Unverified local copy", the API did not answer: you know the
folders and their briefs, not the state. Say that.
</status>