tickets-zordon — serialised tickets, worked as a workflow
One file, TICKETS.md, at the repo root. It is the source of truth. Bugs are
B<n>, features are F<n>, agent-found issues are A<n>, sub-parts are the
parent ID plus a letter (B7a).
Numbers are never reused and never renumbered — an ID means one thing
forever, in commits, branch names, and chat.
The file
Create it if missing, with exactly this shape:
# TICKETS
Legend: `[ ]` pending · `[~]` in-progress · `[%]` testing · `[!]` blocked · `[?]` decide · `[>]` deferred · `[x]` done · `[-]` cancelled
IDs are permanent — never reuse or renumber. Append new tickets at the end of
their section.
## Bugs
- [x] B1 — Login redirect loops on expired session
- [~] B2 — CSV export drops the last row
- [x] B2a — off-by-one in the writer
- [ ] B2b — add regression test
- [!] B3 — Avatar upload 500s over 5MB (blocked: needs S3 creds from ops)
## Features
- [ ] F1 — Dark mode
- [ ] F2 — Bulk delete in the table view
## Agent-found
- [ ] A1 — Unhandled promise rejection in the upload worker (runtime)
- [>] A2 — `parseDate` silently returns Invalid Date on empty string (deferred: after the parser rewrite)
Line format, kept greppable: - [<status>] <ID> — <one-line title>. Optional
trailing (@owner) or (branch: x) if the user wants it, and the
[app: ..] [decide: ..] [owner: ..] [by: ..] tags of Apps and people before it; nothing
else. Sub-parts are indented two spaces under their parent.
The title comes first and is short: at most 60 characters, a name the owner
recognises, ending at the first . or ( — /skillator-pending cuts it there — and the
detail follows. Write the title before the spec.
Good: - [ ] F12 — CSV export. The table view gets an Export button; ....
Bad: - [ ] F12 — The table view gets an Export button that writes the filtered rows ...
(the title is the whole spec, and /skillator-pending shows a cut sentence).
check-tickets.sh warns on every open line whose title is over 60 or empty.
Who touched it
Several agent sessions edit one board, so every line says which one last moved
it, for whom, and how (F109): (@cc-k7q2:asha:direct) - (@<sid>:<owner>:<mode>).
<sid> is <agent>-<code>, the code 4 characters from your session id -
ticket-meta session prints it. Lowest available rung wins:
- Session id — Claude Code's (
CLAUDE_CODE_SESSION_ID) → cc-<code>.
Stable for the session, free, no state to keep.
- No session id in your harness →
SKILLATOR_SESSION=@<agent>-<4 chars> for
the session, or the branch: (branch: fix/upload).
- Both the same across your sessions → ask the user once for a name
(
@cc-ui, @codex-api) and use it for the rest of the session.
<owner> is whoami without @, or - with no team / me unknown.
<mode> is how the work ran: direct (you, at the prompt), agent (a
subagent - say SKILLATOR_MODE=agent on its ticket-meta calls), run
(relay-morpheus flipped it), workflow (a marathon / Workflow script's run).
Agent prefix: cc Claude Code, cx Codex, ag Antigravity, pi Pi, cu Cursor.
ticket-meta stamps it on every write when it knows your session; a line you
create or flip by hand gets the same tag — replace the previous one, don't
accumulate them; the line says who moved it last, not its whole history. Old
(@cc-a4f1c9) tags stay valid: the session alone. Leave a human @owner alone.
Two sessions want the same [ ] ticket: the one whose tag is already on a [~]
row owns it. If a row you are working flips under you, stop and tell the user —
that is two sessions on one ticket, not a merge to resolve.
Apps and people
A ticket can say which apps it touches, who must decide it, who implements it
and who built it — trailing tags on its one line, in this order, before the
session tag:
- [ ] F12 — Bulk delete [app: web, api] [decide: @vidul] [owner: @asha] [by: @vidul, @asha] (@cc-k7q2:asha:direct)
Every tag is optional and lines without them stay valid; never add an empty one.
- People are
@handles from .skillator/team.md, one per line:
- @vidul: vidul@ikran.in, other@x.com. No team file = no people: no
decide/owner/by tags, no assigning, nothing about people in a list.
- Apps are the workspace folders:
apps/*, packages/*, services/*, and
the package manager's workspaces (package.json "workspaces",
pnpm-workspace.yaml); each folder name is an app. No such folder = no apps.
decide = the person who must make a decision on it. owner = the person
who implements it. by = authors of commits whose subject
names the ID as a word (F1 never matches F12), mapped to handles; an email
not in the team file shows as the email. app = apps those commits' files
sit in; it may be hand-set or corrected on the line.
scripts/ticket-meta.sh beside this file does all of it (Windows:
ticket-meta.ps1, same arguments) and edits only the one line, every other byte
kept, in the main checkout's TICKETS.md:
sh <skills>/tickets-zordon/scripts/ticket-meta.sh apps # app names
sh <skills>/tickets-zordon/scripts/ticket-meta.sh app-of <path>.. # app of a path
sh <skills>/tickets-zordon/scripts/ticket-meta.sh by F12 # who built it
sh <skills>/tickets-zordon/scripts/ticket-meta.sh apps-of F12 # apps it touched
sh <skills>/tickets-zordon/scripts/ticket-meta.sh assign F12 @asha # implements it
sh <skills>/tickets-zordon/scripts/ticket-meta.sh decide F12 @asha # must decide it
sh <skills>/tickets-zordon/scripts/ticket-meta.sh decided F12 # decision made
sh <skills>/tickets-zordon/scripts/ticket-meta.sh testing F12 owner live check # [%], waits on that test
sh <skills>/tickets-zordon/scripts/ticket-meta.sh tested F12 pass # [%] -> [x]; fail -> [~]
sh <skills>/tickets-zordon/scripts/ticket-meta.sh done F12 RED/GREEN 3/3, abc1234 # [x] + tag, ` **Done <date>: ..**`
sh <skills>/tickets-zordon/scripts/ticket-meta.sh block F12 S3 creds from ops # [!] ` (blocked: ..)`
sh <skills>/tickets-zordon/scripts/ticket-meta.sh defer F12 after the parser rewrite # [>] ` (deferred: ..)`
sh <skills>/tickets-zordon/scripts/ticket-meta.sh tag F12 # write app + by
sh <skills>/tickets-zordon/scripts/ticket-meta.sh whoami # F80: my @handle; F109: + session: @<sid> mode:
sh <skills>/tickets-zordon/scripts/ticket-meta.sh iam @asha # F92: this session's owner
sh <skills>/tickets-zordon/scripts/ticket-meta.sh stamp F12 # F109: the (@sid:owner:mode) tag only
sh <skills>/tickets-zordon/scripts/ticket-meta.sh session # F109: <sid> <mode>
sh <skills>/tickets-zordon/scripts/ticket-meta.sh pick F12 F14 # F80: pick / skip <ID> <owner>
sh <skills>/tickets-zordon/scripts/ticket-meta.sh claim F12 # F80: [owner: <me>], box kept
sh <skills>/tickets-zordon/scripts/ticket-meta.sh team lead @asha # F80: set / hand over the lead
sh <skills>/tickets-zordon/scripts/ticket-meta.sh reconcile # F81: read-only, `ID [now] -> [proposed] reason`
sh <skills>/tickets-zordon/scripts/ticket-meta.sh unblock F12 # F81: [!] -> [ ], the blocked note dropped
sh <skills>/tickets-zordon/scripts/ticket-meta.sh start F12 # F81: [ ] -> [~]; F106: claims an unowned ticket to me, says when another owns it
The team file is kept with ticket-meta team add @h "Name" email[,email],
team remove @h and team list. A member line is - @handle: a@x, b@y, with an
optional indented name: Full Name line directly under it. team remove warns,
and still removes, when open tickets still name the handle.
Roles, me, claims (F80). The format, in full:
# Team
lead: @vidul
- @vidul: vidul@ikran.in
name: Vidul
- @asha: asha@x.com
- One lead: the one
lead: @handle line under # Team (a team file without
it is valid: no lead). Everyone else listed is a member. team lead @h sets it
when there is none, or hands it over when me is the lead; team lead - clears
it (the lead only). team remove of the lead is refused until it is handed over.
team list marks [lead] and (you).
- Me:
ticket-meta whoami reads, in order, this session's owner (F92:
ticket-meta iam @handle, asked at session start by grayskull-power's arm,
kept in git-ignored .skillator/sessions/<sid>.owner - line 1 the handle,
line 2 session: <id>, a file naming another session ignored; the sid from
SKILLATOR_SESSION, else Claude Code's session id → cc-<4-char code>), then
SKILLATOR_ME=@handle, then this repo's git user.email through the team
emails. A handle not on the team is refused. No match → not on the team: add <email> to .skillator/team.md.
- Claims: planning or dispatching a ticket (relay-morpheus
chain plan /
chain dispatch, /pending-sentinel, /gauntlet-plan) runs
ticket-meta claim <ID>... — [owner: <me>], the box kept. A ticket already
owned by someone else is reassigned (assign or claim) only by that owner or
the lead; anyone else is refused, the refusal naming both. Not on the team →
claims are refused (add <email> to team.md).
- Picking:
ticket-meta pick [IDs] prints you: <me> then pick <ID>
(unassigned, or mine) or skip <ID> <owner> per ticket (no IDs: every [ ]
[~] [!] ticket). Runs take only the picked; a skipped one is listed as
skipped with its owner, never run. Not on the team → only unassigned tickets.
No team file → every ticket is picked and nothing is claimed, as before.
- These checks are a team convention, not security: git's email is self-set
and anyone can edit
team.md or TICKETS.md by hand. They stop honest
mistakes - two people running one ticket - not a determined teammate.
An assignment reopens the ticket. Whoever it moves to, it must not stay
closed, deferred or in someone else's progress:
- "assign F12 to @asha", "assign it to asha" →
assign: sets or replaces
[owner: ..] and the box becomes [ ], from any state.
- "assign it for a decision to @asha", "Asha decides F12" →
decide: sets or
replaces [decide: ..] and the box becomes [?], from any state.
- "decided", "Asha decided F12" →
decided: [?] back to [ ]; the
[decide: ..] tag stays as the record. It refuses a ticket that is not [?].
- The same handle again for the same kind, with the box already
[ ] (assign)
or [?] (decide), changes nothing and says no change; any other box still
moves.
- Moving a
[~] ticket keeps its trailing session tag (@cc-…) or (@cc-…:…:…) beside the new
[owner:]/[decide:] — which session works it and who owns it are different
facts — and warns which session was working it; tell that session its box
moved. A relay lease is per stage and is released when that stage lands or fails.
- Both refuse a handle not in the team file — say so, and offer to add the
person there; never invent one.
assign of a ticket someone else owns is refused unless me is that owner
or the lead (F80, above) — say who may, never edit the line by hand around it.
tag <ID> when a ticket is closed ([x]), and when commits naming it land
(a merge, a pull). It recomputes app and by from the commits; with none it
leaves a hand-set app alone.
done, block, defer (F64) set [x], [!], [>] from any box but a
cancelled [-]; block and defer also refuse a done [x] (reopen with
assign). block/defer replace an earlier (blocked: ..) or
(deferred: ..) note — the line says only the current wait — and the same
text again on the same box says no change. Tags, other notes and the session
tag stay; leaving [~] warns like assign.
- Every edit prints the edited line — that is the read-back. All write under
TICKETS.md.lock, the lock relay-morpheus's board flip takes, and refuse
after 30 s rather than break someone else's.
- Tags go before the trailing
(..) groups and before a bare Plan: S<n>, so
check-tickets.sh still sees that pointer.
Allocating an ID
Never take "highest on my board + 1" by hand: two worktrees or sessions that do
not share a TICKETS.md both get the same number. Run the allocator from the
repo root; it prints the number and reserves it before you write the line:
sh "$PRACTICE/scripts/next-id.sh" A # --peek A: look without reserving
$PRACTICE is the practice/ beside the installed skills — resolve it exactly as
practice/task-loop.md resolves taskwork.sh (Windows: next-id.ps1 A,
-Peek). It takes 1 + the max of the local board and its archive (done and
archived tickets count — closing never frees a number), both files on every local and remote-tracking ref, and a
counter in the clone's common git dir shared by every worktree, under a lock.
Cross-machine is best-effort: it sees only refs you have fetched, so git fetch
first on a shared branch. Sub-parts (B2a, B2b, …) are the next unused letter
under the parent, by hand — only for genuinely separate pieces.
Collision rule: if two teammates ever land the same number, the later commit
renames its ticket to a fresh number and leaves (was B7) on the line. Never
renumber the earlier one. In a merge, "earlier" is the receiving branch: its IDs
never move; the incoming side's do.
The board ships with the work. TICKETS.md (and TICKETS-archive.md) is
committed in the same commit as the change it describes and pushed with it —
never held back, never gitignored. A board that stays local is a board the next
clone allocates against blind.
Arm the merge guard — once per clone, when this skill arms. Git hooks and
merge drivers live in .git/, not in the repo, so a git pull does not bring
them; run this the first time you touch the board in a clone (idempotent —
re-running only refreshes it, so run it every session that arms):
sh "$PRACTICE/scripts/renumber-tickets.sh" --install
It copies the script into the clone's common git dir and wires a tickets merge
driver for TICKETS.md and TICKETS-archive.md (two branches that both appended
merge as the union, not a conflict; two edits of one ticket stay a conflict) plus
post-merge and pre-commit hooks. From then on a plain git pull or git merge
that brings in an ID the receiving branch already has ends correct with no manual
step: the incoming ticket takes the next free number (archive included) with
(was F2), its sub-parts move with it, references are rewritten only in files
the incoming side changed, and the change lands in the merge commit, its
map: lines appended to the message and to .git/skillator/renumber.log. If
core.hooksPath points outside the clone it installs the driver only and says so
— never write into a shared hooks dir. git pull --rebase and cherry-pick are
not covered; merge-smith runs the same script itself. On a diverged branch a
bare git pull stops before merging unless pull.rebase is set, so pull with
--no-rebase (or git config pull.rebase false) for the guard to run.
A teammate who never runs a skill has no driver and no hooks: their pull either
conflicts on the board or merges both F2 lines silently. check-tickets.sh
below is what catches it, and renumber-tickets.sh (inside the merge, before its
commit) is the fix.
Detect it at merge time. Git merges the append-only board by keeping both
sides of an A43 conflict — the obvious resolution and the wrong one. After
any merge, rebase, or cherry-pick that touched TICKETS.md, and before
committing one: sh "$PRACTICE/scripts/check-tickets.sh" TICKETS.md — name
the board to check another; bare, it checks the current git repo's top-level TICKETS.md (./TICKETS.md outside git). It fails on
duplicate IDs and committed conflict markers and prints the offending lines. A
clean board is a precondition for allocating, not a nicety.
When to log
- User reports a bug → log a
B ticket before fixing.
- User asks for a feature/change of any size → log an
F ticket before building,
then invoke skillator:build-jarvis with that ticket. The board logs;
build-jarvis grades, designs and builds. Never build an F ticket inline here.
- Anything Claude/an agent finds itself → an
A ticket, if it passes the gate
below. A stack trace in a test run, a crash while driving the app, a bug
spotted during review: log it as pending and keep going. A means "nobody
asked for this, we found it" — it is what keeps discoveries from dying with
the chat.
A non-feature one-line edit the user asked for inline (typo, comment, rename,
formatting) needs no ticket and goes direct. A feature of any size is an F.
The gate — a ticket names a change, not a finding
A pending line is not cheap. It is a promise to whoever reads the board next,
and a board that grows faster than it drains stops being read at all — at which
point every row on it is worth nothing, including the real ones.
Before logging, say the change out loud in one sentence: "someone should edit
X so that Y." If you can't finish that sentence, it isn't a ticket:
| What you have |
Where it goes |
| A change you can name, that nobody has made |
Ticket. |
| Something true about the code that implies no edit |
Say it in chat. Nothing to log. |
| A risk with no reproduction and no fix to try |
Say it in chat, with what would settle it. Not a ticket. |
| Already fixed in the tree — you just found the fix |
Nothing. |
| The same defect as an open row, seen from elsewhere |
Nothing; that row already covers it. |
| Work you are about to do in this same turn |
Do it. A ticket you close a minute later is noise. |
An agent's report is input, not a row. Reports arrive one per agent, so
converting each into a ticket inflates the board at exactly the rate you spawn
agents. Read the report, apply the gate to every item in it, and log the ones
that pass — normally fewer than were reported. Say in chat what you dropped and
why; that is the audit trail, not a row.
Two failure modes, both worse than a missing ticket: the same defect logged
three times because three agents saw it, and a row so vague nobody can tell
what "done" would mean. If you can't write the closing condition, you can't
write the ticket.
Working a ticket
- Starting →
ticket-meta start <ID>: [~], an unowned ticket claimed to you (F106), your session tag stamped (F109; a subagent prefixes SKILLATOR_MODE=agent), see Who touched it.
- Finished and verified (tests/build/manual check actually run) →
[x],
via ticket-meta done <ID> [evidence]: the box [x], the tag a close owes,
and, when evidence is given, **Done <YYYY-MM-DD>: <evidence>** before the
session tag (it replaces an earlier Done note). The evidence is one line with
no parentheses and no * — ticket-meta refuses them — so write a commit,
a test result or a quote without them: RUN-0017 stage 110, bd408c6, not
(RUN-0017, bd408c6); sweep PASS 8/8, not **PASS** (8/8). It refuses a
cancelled [-] ticket - reopen it with assign first.
Not verified, not done.
- Built, but the verifying test has not run yet and is not yours to run now —
an owner's live check, a GREEN on another host, a CI run →
[%] testing,
via ticket-meta testing <ID> <what test>, which writes
(testing: <what test>) on the line (one line, no parentheses). Testing is
open: report it at session end, and never build on it as if done. It
leaves only on the result: ticket-meta tested <ID> pass → [x],
tested <ID> fail → back to [~] to fix; the (testing: ..) note stays as
the record. Not for a test you can run yourself this turn — run it.
- Can't proceed — waiting on someone, a credential, an upstream fix, or another
ticket →
[!], with (blocked: <what on>) on the line, via
ticket-meta block <ID> <what on>. Blocked is still
open: report it at session end, and unblock back to [ ] or [~] the
moment the dependency clears. Never leave an agent spinning on a blocked
ticket — flip it and move to the next one.
- Waiting on a person's decision (which option, whether to do it at all) →
[?] decide, via ticket-meta decide <ID> @who so the line names
who decides. Decide is open, like blocked: report it at session
end, never build it before the decision, and flip it to [ ] with
ticket-meta decided <ID> once the answer is in.
- Postponed by choice — not now, waiting on a condition that isn't a hard
dependency (a later milestone, a build that hasn't run, hardware not on the
bench) →
[>], with (deferred: <until what>) on the line, via
ticket-meta defer <ID> <until what>. Deferred is
not open and not closed — it is off the board until the condition
arrives: not pending (nobody is picking it up next), not blocked (nobody owes
you anything), not cancelled (it will be done). Report it at session end as
its own line, and flip it back to [ ] when the condition arrives.
- Dropped — won't fix, obsolete, duplicate, or the user called it off →
[-],
with a short — reason on the line ([-] B9 — Safari flicker (dup of B4)).
Cancelled is a closed state, not a deleted one: the line and its number stay.
- Reference the ID in commit messages:
B3: reject uploads over 5MB — that
subject is how by and app find the work. Closing it → tag <ID>
(Apps and people).
- A board edit is not done until you have read it back. After every status
flip,
grep -n '<ID>' TICKETS.md and report from that output, never from the
edit you believe you made. An edit whose hunk is missing from git diff is a
failed flip, not a done one — silent no-ops are routine here, because
TICKETS.md is UTF-8 and full of em dashes, so any tool that reads it as
cp1252 (a bare Python open() on Windows) matches nothing and changes
nothing while exiting 0. Read, write and compare it as UTF-8.
- Cycle end / session end: re-read the file and correct any status that drifted,
then report the open set — every open box:
[ ], [~], [%], [!] and
[?] — to the user.
- Once the turn's edits are read back, republish the artifact board — see
The artifact board. Board changed, artifact stale, is a bug.
Draining the board
Pending rows are not immortal, and a rising pending count is a symptom to
diagnose — not a backlog to admire. Run a drain before any handover, release,
or mergeprep-oracle, and whenever a single session has added more pending rows than
it closed. (Both are checkable on the spot; "has it grown since last time" is
not — no prior count is stored anywhere.) A drain re-verifies the pending rows
against the tree, not against their own text:
- Fix is already in the tree →
[x], citing where. Reading the fix is not
verifying it: [x] still means what it means above — run the check. If you
can only see the code, leave it pending and say the fix looks present.
- No change can be named for it (it was an observation) →
[-] — (not work: <why>).
- Same defect as another row →
[-] — (dup of <ID>).
- Still real → leave it, and make the line name the change.
Sweep [>] rows in the same pass — that is where stale rows collect, since a
deferred row is off the board until a condition arrives and nothing checks
whether it already has. For each, ask only "has the condition arrived?": yes →
[ ], no → leave it, never going to → [-].
A row that states its defect confidently is still wrong if a later commit fixed
it, so check the code, never the wording. Rows leave the board only through a
status flip — never by deletion; the archive below moves closed rows, it never
drops one.
Report the drain as a count: pending 12 → 5 (3 already fixed, 3 not work, 1 dup).
Archive what has stayed closed
A board that keeps every closed row grows until reading it costs more than the
work it tracks. Archive every time this skill arms — the first board read of
a session, before reporting the open set — and again at the end of a drain or
release. A step left to "the end of a drain" never runs; this board reached
110 KB that way.
sh "$PRACTICE/scripts/archive-tickets.sh" --dry-run # list what would move
sh "$PRACTICE/scripts/archive-tickets.sh" # move it
Moved anything → run check-tickets.sh, then commit TICKETS.md and
TICKETS-archive.md together, in their own commit (tickets: archive N closed), and push them with the session's next push. One without the other is
a clone that loses tickets or reuses IDs. Moved nothing → say nothing.
[x] and [-] rows closed more than 14 days ago (--days N) move to
TICKETS-archive.md beside the board, under the same section heading. The
closing date is the commit that flipped the status, read from git — lines carry
no date. A parent stays until it and every sub-part are closed and old enough,
then they move together. The archive is committed with the board and never
edited by hand.
Sessions read only TICKETS.md. The allocator, check-tickets.sh and the
artifact board read both files, so an archived number is never reused and a
duplicate across the two still fails. For an old ID the board does not show,
grep -n '<ID>' TICKETS-archive.md before saying it does not exist.
Sync what is in progress (/sync-zordon)
[~] collects rows that are really done, waiting on a test, stuck or parked,
because nothing flips them back; [!] and [ ] rows go stale the same way. On
/sync-zordon (or "sync tickets"), walk every [!], [ ] and [~] row —
or only the IDs given as arguments — and propose the status it really has.
Propose from evidence, never invent it.
Start from ticket-meta reconcile [IDs] (F81, read-only - the ops
board's c key runs the same rule). It prints ID [now] -> [proposed] reason per row with evidence: a [!] whose (blocked: ..) names tickets
all [x] → [ ]; a check owed by the owner or a team (a (testing: ..)
note, a live check, a release build, a device / rig / hardware, a team to
confirm) with the code landed → [%]; a run stage on it failed, or silent
a day → [!]; landed → [%]; a [ ] with commits on main led by its ID
(F81:, not board: ones) → [~]. Landed is the ticket's last run stage
x, or with no stage a commit; a [!] still blocked on an open ticket is
never [%]. A row it keeps says "evidence unclear". It never proposes
[x] and skips a [~] row with a session tag. Its rows go in the table as
they are; steps 1-2 add what it cannot see ([x], [>], [?], a [~]
the line shows done).
For each [~] row read its line and its notes (Done = .., Progress ..,
Owed .., blocked, waiting on), then git log --oneline -F --grep=<ID>
(keep only subjects naming the ID as a word — F1 is not F12) and any
practice/baselines file or run file (.skillator/run-*.md) the line cites.
Propose exactly one:
| Proposal |
Only when |
[x] done |
the line's Done criterion is shown met by named evidence — a commit, a test result, an owner confirmation quoted on the line. Cite it, and write it without parentheses or * (see step 4). |
[%] testing |
built, and a named test or check is still owed (an owner's live check, another host's GREEN, a CI run) — (testing: <what>) |
[!] blocked |
it cannot proceed until something outside it lands — (blocked: <on what>) |
[>] deferred |
postponed by choice until a condition — (deferred: <until what>) |
[?] decision |
it waits on a person's choice — name who decides |
stays [~] |
still being worked: a session tag on the line ((@cc-a4f1c9) or (@cc-k7q2:asha:run), any agent prefix, any shape — reason "worked by @cc-a4f1c9"), a commit naming it in the last 24 hours, or a run stage on it dispatched and not done |
stays [~], "evidence unclear" |
anything else. Unsure is not done. |
A [~] row carrying a session tag is held by that session: it stays [~]
("worked by @cc-xxxx") and is never proposed for another status, whatever
its notes or commits say — unless the user names that ID in the command's
arguments or in the answer.
Show one table — ID | now -> proposed | reason (the evidence, one line)
— then ask once: accept all / pick (which IDs) / none. No question tool
on the host → print the choices as a numbered list and stop.
Apply only the accepted rows, and only on the user's answer. Headless
(claude -p, a chained or relay stage), or the question comes back
unanswered → propose only, apply nothing, and say applied: none (headless).
[%] → ticket-meta testing <ID> <what test>.
[?] → ticket-meta decide <ID> @who. With no .skillator/team.md
(decide refuses) do not flip the box by hand: leave the row [~] and
say in the report who decides and that decide needs a team file. Only if
the user then asks for it: ticket-meta team add @who "Name" <email>
(it creates the team file), then decide.
[x] → ticket-meta done <ID> <the evidence> (it tags the ticket too),
the evidence written without parentheses or *.
[!] → ticket-meta block <ID> <on what>.
[!] → [ ] → ticket-meta unblock <ID>; [ ] → [~] → ticket-meta start <ID>.
[>] → ticket-meta defer <ID> <until what>.
- Never hand-edit a box ticket-meta has a subcommand for.
- Stamp your session tag on every flipped row (Who touched it) - ticket-meta does it when it knows your session.
Read the board back — grep -n '<ID>' TICKETS.md for every applied ID —
run sh "$PRACTICE/scripts/check-tickets.sh", and report from that output: in progress 14 -> 6 (3 done, 2 testing, 1 blocked, 1 deferred, 1 decision).
Verify what is in testing (/verify-shifu)
[%] says built, a check owed. On /verify-shifu (or "verify the testing
tickets"), re-check every [%] row - or only the IDs given; a named ID not
in [%] is reported not [%] and skipped - against evidence obtained now,
never against the line's own claim.
- One fresh agent per ticket, no session history, its own prompt: the ID,
the line verbatim, the repo root. A read-only agent type where the host has
one; no subagents on the host → check each ticket yourself in turn, same
rules. The prompt says:
- Read the line's Done criterion (
Done = .., the (testing: ..) note) and
check every part of it: git log --oneline -F --grep=<ID> (subjects naming
the ID as a word), the files and baselines it cites, and run the tests
or checks it names. Evidence is what you saw this run, never a quote of the line.
- Read and run tests only - never edit code, write or delete files in the
repo, commit, or touch
TICKETS.md. A check that would need an edit to run
is not run: FAIL, "needs an edit to check".
- Answer exactly
VERDICT: PASS|FAIL|OWNER and EVIDENCE: <one line> (no
parentheses, no *), and on FAIL also WHY: <one line> - why it failed,
when you can tell. PASS only when every part is shown met. Anything
failing, missing or not runnable is FAIL, the EVIDENCE line naming what failed.
OWNER when any part needs the owner's own eyes - testing: owner .., a
live look, a picker or UI check, an account or credentials, a device - even
if the rest passed.
--deep only (/verify-shifu --deep [IDs]; off by default): after
the Done check, judge the ticket's code. The commits naming the ID as a
word, board: commits left out, give the range <oldest>^..<newest>; run
code-vader on it (code-vader.sh collect --range <oldest>^..<newest>,
Windows code-vader.ps1 collect -Range ..) and its two lenses, charging
the ticket only for lines its own commits wrote (git show <sha> each -
the range can hold other tickets' commits), plus a design-principles lens: single
responsibility, coupling and cohesion, naming, error handling at trust
boundaries, tests that pin behaviour (not internals), .sh/.ps1 twins in
step. Same severities. PASS only when the Done line is met and no
critical or high finding; else FAIL, EVIDENCE the top findings (at most
three, worst first) as <file:line> - <why> joined by ; , reworded
without parentheses or * as ticket-meta needs, no separate WHY (each
finding carries its own). OWNER still wins.
- Record each verdict in the main session, with ticket-meta only - the
owner's standing ruling, so no question first, headless included. A verdict
is a note, never a status: the box stays
[%] on every verdict (closing it
stays the owner's done). The note replaces any earlier verify note:
- PASS →
ticket-meta verify <ID> pass <evidence>:
(verified PASS <date>: <evidence>) on the line.
- FAIL →
ticket-meta verify <ID> fail <what failed> - <why> ( - <why>
only when the agent gave a WHY): (verified FAIL <date>: <what> - <why>).
- OWNER → nothing. No note.
- An agent that returns no verdict line is FAIL, "no verdict"; never PASS.
- Read the board back -
grep -n '<ID>' TICKETS.md per ticket - run
sh "$PRACTICE/scripts/check-tickets.sh", and report one table
ID | verdict | evidence and the count: testing 3 (1 pass, 1 fail, 1 owner).
Work tickets in parallel, not in a line
An F ticket is built by skillator:build-jarvis, never here. Before any
edit for one — logged a minute ago, picked from the board, or named in a
headless "work these tickets" — invoke build-jarvis with its id and title. Its
grade line is that ticket's tiering, its phases are the dispatch. Several
F tickets are ONE build-jarvis pass, one task block per ticket — never one
build-jarvis per ticket. "One agent per ticket" below means, for an F, that
ticket's build seat is one dispatched agent inside that pass: it gets the pass's
grade and its own task block, and implements only that (no regrade, no verify of
its own, never build-jarvis loaded as an orchestrator). "It is only a few lines"
is the grade's call (a — design seat, a cheap build), not a reason to skip it.
B and A tickets stay on this page's dispatch below.
Flipping a ticket to [~] means dispatch an agent for it, one agent per
ticket, all in a single message so they run concurrently (for F tickets,
build-jarvis's Phase 2 does that dispatch). Never work a queue of tickets
serially in the main session — that is the linear development this skill exists
to break.
- Give each agent its ticket ID, the one-line title, and the repo context it
needs; tell it to report back what it changed and whether it verified (an F
build seat: which of its task's tests it ran - the verify seat is not its).
- Name a model for every dispatch — never let it inherit the session's, and
grade the tier per ticket, not once for the batch. Same table as workflow
mode's scout (below); a mechanical fix and the agent judging it warrant
different tiers, and so do two tickets in the same message.
- Only the main session edits
TICKETS.md — agents report, you flip statuses.
Two agents writing the same file is how you lose tickets.
- Tickets touching the same files are the one exception: run those sequentially,
or hand the whole cluster to one agent, and say so.
- Sub-parts (
B2a, B2b) are the unit to parallelise when a ticket is big.
Workflow mode — working the board in one call
Dynamic workflows let you write a script that orchestrates many agents
deterministically: real control flow, structured results, a resumable run. Same
board as plain dispatch, scripted.
Ask the mode once before a sweep. When this cycle has 4+ open tickets to
work, or the tickets are a sweep, settle how they run before the first [~]
flip or dispatch:
| Mode |
What runs |
Fits |
| single |
One dispatched agent works the cycle's tickets in order — never the main session |
Tightly coupled tickets, tickets sharing files |
| per-task |
Plain dispatch: one agent per ticket, all in one message (above); same-file tickets stay one item |
Independent tickets — the usual pick when nothing else fits |
| workflow |
The script in "The shape" below; no Workflow tool → the host's parallel delegate, never claimed as a Workflow call |
4+ independent tickets or a sweep — costs the most tokens |
A sweep reached through relay-morpheus also offers marathon (its
references/marathon.md): the staged form of workflow that keeps going across
sessions.
Ask once: all three modes, your recommendation first (AskUserQuestion; no
such tool → a numbered list). Then end your turn — no [~] flip, no
dispatch, until the user answers. No question when the user already named a
mode ("ultracode", "use a workflow", "fan out agents", "one agent per ticket",
"single agent") — use it. No question when the mode was already answered this
turn (by the user, or by relay-morpheus's references/marathon.md entry) —
don't re-ask. No question when the run is headless, chained or inside a relay —
take your recommendation, capped at per-task unless the user named workflow,
and log Ruling: mode <m> - <why> - <cost if wrong>. Unasked, the most you
pick is per-task.
F tickets in the sweep still go to ONE build-jarvis pass, handed the
sweep's answer as a named mode, so the user is asked once.
Recommend workflow when any of these hold:
- 4+ open tickets to work in this cycle (real fan-out).
- The tickets are a sweep — the same change across N files, an audit, a codemod.
- You want each fix adversarially verified before flipping it to
[x].
- The user asked: "ultracode", "use a workflow", "fan out
agents", "orchestrate this with subagents".
Stay with plain dispatch when: 1-3 tickets (no question — per-task, as
today), tickets needing your judgement between them, or a host with no
Workflow tool. Off claude-code, workflow mode
is a pattern — emulate it with the host's parallel delegate mechanism and don't
claim a Workflow call happened. See WORKFLOW.md beside the installed skills
for the host table.
Never start a workflow the user didn't opt into. A workflow can spawn dozens
of agents; if the board is big and they didn't ask, say what it would cost first.
Several workflows in a row, each starting the next with a usage hold —
"work every open ticket in staged workflows, keep going" — is relay-morpheus →
references/chain.md; the board rules on this page do not change there.
The shape
Scout inline first — read TICKETS.md, pick the tickets for this cycle, group
same-file tickets into one item, and tier each one — then pass that list as
args and let the script fan out. pipeline() is the default: ticket B is being
verified while ticket C is still being fixed.
Tier every ticket during the scout
A flat model: across the fan-out is the expensive mistake this section exists
to prevent: it pays deep-tier price for one-line fixes, or hands a contract
change to a cheap model that burns 3× the turns and fails anyway. The scout
assigns a tier per ticket per seat — you have already read the ticket, so
grading it costs nothing extra — and the script reads that off the item.
Grade the fix seat from the ticket's own text, using PRACTICE.md §4 and
practice/task-loop.md — the same table, applied per ticket:
| The ticket reads like |
fix |
verify |
| One file, mechanical, the change is named in the ticket |
cheap |
build |
| 1-2 files, complete spec, nothing to decide |
cheap |
build |
| Several files, integration or a shared contract |
build |
build |
| Cause unknown, design judgement, or "sweep every X" |
deep |
deep |
| Concurrency, auth, money, or a contract others depend on |
build |
deep |
…(truncated)
1---2name: tickets-zordon3description: >-4 Use when the user reports a bug or asks for a feature, says "log this",5 "what's pending", "ticket", "B3", "F12", "A4", "next ticket number", "mark6 it done", "block it", "defer it", "cancel it", "list tickets", "list tickets7 status", "sync tickets", "assign F12 to @asha", "ultracode", "use a workflow",8 mentions TICKETS.md, or when starting work needing the open set. Also9 at session end, to sync statuses. NOT an issue tracker or Jira/GitHub sync;10 NOT for harvesting `ponytail:` markers (`code-yoda`).11metadata:12 source: https://skillmd.com/skills/bodish-coder/tickets-zordon13---1415# tickets-zordon — serialised tickets, worked as a workflow1617One file, `TICKETS.md`, at the repo root. It is the source of truth. Bugs are18`B<n>`, features are `F<n>`, agent-found issues are `A<n>`, sub-parts are the19parent ID plus a letter (`B7a`).20Numbers are **never reused** and **never renumbered** — an ID means one thing21forever, in commits, branch names, and chat.2223## The file2425Create it if missing, with exactly this shape:2627```markdown28# TICKETS2930Legend: `[ ]` pending · `[~]` in-progress · `[%]` testing · `[!]` blocked · `[?]` decide · `[>]` deferred · `[x]` done · `[-]` cancelled31IDs are permanent — never reuse or renumber. Append new tickets at the end of32their section.3334## Bugs3536- [x] B1 — Login redirect loops on expired session37- [~] B2 — CSV export drops the last row38 - [x] B2a — off-by-one in the writer39 - [ ] B2b — add regression test40- [!] B3 — Avatar upload 500s over 5MB (blocked: needs S3 creds from ops)4142## Features4344- [ ] F1 — Dark mode45- [ ] F2 — Bulk delete in the table view4647## Agent-found4849- [ ] A1 — Unhandled promise rejection in the upload worker (runtime)50- [>] A2 — `parseDate` silently returns Invalid Date on empty string (deferred: after the parser rewrite)51```5253Line format, kept greppable: `- [<status>] <ID> — <one-line title>`. Optional54trailing ` (@owner)` or ` (branch: x)` if the user wants it, and the55`[app: ..] [decide: ..] [owner: ..] [by: ..]` tags of **Apps and people** before it; nothing56else. Sub-parts are indented two spaces under their parent.5758The title comes first and is short: at most 60 characters, a name the owner59recognises, ending at the first `. ` or ` (` — /skillator-pending cuts it there — and the60detail follows. Write the title before the spec.61Good: `- [ ] F12 — CSV export. The table view gets an Export button; ...`.62Bad: `- [ ] F12 — The table view gets an Export button that writes the filtered rows ...`63(the title is the whole spec, and /skillator-pending shows a cut sentence).64`check-tickets.sh` warns on every open line whose title is over 60 or empty.6566## Who touched it6768Several agent sessions edit one board, so every line says which one last moved69it, for whom, and how (F109): ` (@cc-k7q2:asha:direct)` - `(@<sid>:<owner>:<mode>)`.7071- `<sid>` is `<agent>-<code>`, the code 4 characters from your session id -72 `ticket-meta session` prints it. Lowest available rung wins:73 1. **Session id** — Claude Code's (`CLAUDE_CODE_SESSION_ID`) → `cc-<code>`.74 Stable for the session, free, no state to keep.75 2. No session id in your harness → `SKILLATOR_SESSION=@<agent>-<4 chars>` for76 the session, or the branch: ` (branch: fix/upload)`.77 3. Both the same across your sessions → ask the user once for a name78 (`@cc-ui`, `@codex-api`) and use it for the rest of the session.79- `<owner>` is `whoami` without `@`, or `-` with no team / me unknown.80- `<mode>` is how the work ran: `direct` (you, at the prompt), `agent` (a81 subagent - say `SKILLATOR_MODE=agent` on its ticket-meta calls), `run`82 (relay-morpheus flipped it), `workflow` (a marathon / Workflow script's run).8384Agent prefix: `cc` Claude Code, `cx` Codex, `ag` Antigravity, `pi` Pi, `cu` Cursor.8586ticket-meta stamps it on every write when it knows your session; a line you87create or flip by hand gets the same tag — replace the previous one, don't88accumulate them; the line says who moved it last, not its whole history. Old89`(@cc-a4f1c9)` tags stay valid: the session alone. Leave a human `@owner` alone.9091Two sessions want the same `[ ]` ticket: the one whose tag is already on a `[~]`92row owns it. If a row you are working flips under you, stop and tell the user —93that is two sessions on one ticket, not a merge to resolve.9495## Apps and people9697A ticket can say which apps it touches, who must decide it, who implements it98and who built it — trailing tags on its one line, in this order, before the99session tag:100101```102- [ ] F12 — Bulk delete [app: web, api] [decide: @vidul] [owner: @asha] [by: @vidul, @asha] (@cc-k7q2:asha:direct)103```104105Every tag is optional and lines without them stay valid; never add an empty one.106107- **People** are `@handles` from `.skillator/team.md`, one per line:108 `- @vidul: vidul@ikran.in, other@x.com`. No team file = no people: no109 `decide`/`owner`/`by` tags, no assigning, nothing about people in a list.110- **Apps** are the workspace folders: `apps/*`, `packages/*`, `services/*`, and111 the package manager's workspaces (`package.json` `"workspaces"`,112 `pnpm-workspace.yaml`); each folder name is an app. No such folder = no apps.113- `decide` = the person who must make a decision on it. `owner` = the person114 who implements it. `by` = authors of commits whose subject115 names the ID as a word (`F1` never matches `F12`), mapped to handles; an email116 not in the team file shows as the email. `app` = apps those commits' files117 sit in; it may be hand-set or corrected on the line.118119`scripts/ticket-meta.sh` beside this file does all of it (Windows:120`ticket-meta.ps1`, same arguments) and edits only the one line, every other byte121kept, in the main checkout's `TICKETS.md`:122123```sh124sh <skills>/tickets-zordon/scripts/ticket-meta.sh apps # app names125sh <skills>/tickets-zordon/scripts/ticket-meta.sh app-of <path>.. # app of a path126sh <skills>/tickets-zordon/scripts/ticket-meta.sh by F12 # who built it127sh <skills>/tickets-zordon/scripts/ticket-meta.sh apps-of F12 # apps it touched128sh <skills>/tickets-zordon/scripts/ticket-meta.sh assign F12 @asha # implements it129sh <skills>/tickets-zordon/scripts/ticket-meta.sh decide F12 @asha # must decide it130sh <skills>/tickets-zordon/scripts/ticket-meta.sh decided F12 # decision made131sh <skills>/tickets-zordon/scripts/ticket-meta.sh testing F12 owner live check # [%], waits on that test132sh <skills>/tickets-zordon/scripts/ticket-meta.sh tested F12 pass # [%] -> [x]; fail -> [~]133sh <skills>/tickets-zordon/scripts/ticket-meta.sh done F12 RED/GREEN 3/3, abc1234 # [x] + tag, ` **Done <date>: ..**`134sh <skills>/tickets-zordon/scripts/ticket-meta.sh block F12 S3 creds from ops # [!] ` (blocked: ..)`135sh <skills>/tickets-zordon/scripts/ticket-meta.sh defer F12 after the parser rewrite # [>] ` (deferred: ..)`136sh <skills>/tickets-zordon/scripts/ticket-meta.sh tag F12 # write app + by137sh <skills>/tickets-zordon/scripts/ticket-meta.sh whoami # F80: my @handle; F109: + session: @<sid> mode:138sh <skills>/tickets-zordon/scripts/ticket-meta.sh iam @asha # F92: this session's owner139sh <skills>/tickets-zordon/scripts/ticket-meta.sh stamp F12 # F109: the (@sid:owner:mode) tag only140sh <skills>/tickets-zordon/scripts/ticket-meta.sh session # F109: <sid> <mode>141sh <skills>/tickets-zordon/scripts/ticket-meta.sh pick F12 F14 # F80: pick / skip <ID> <owner>142sh <skills>/tickets-zordon/scripts/ticket-meta.sh claim F12 # F80: [owner: <me>], box kept143sh <skills>/tickets-zordon/scripts/ticket-meta.sh team lead @asha # F80: set / hand over the lead144sh <skills>/tickets-zordon/scripts/ticket-meta.sh reconcile # F81: read-only, `ID [now] -> [proposed] reason`145sh <skills>/tickets-zordon/scripts/ticket-meta.sh unblock F12 # F81: [!] -> [ ], the blocked note dropped146sh <skills>/tickets-zordon/scripts/ticket-meta.sh start F12 # F81: [ ] -> [~]; F106: claims an unowned ticket to me, says when another owns it147```148149The team file is kept with `ticket-meta team add @h "Name" email[,email]`,150`team remove @h` and `team list`. A member line is `- @handle: a@x, b@y`, with an151optional indented ` name: Full Name` line directly under it. `team remove` warns,152and still removes, when open tickets still name the handle.153154**Roles, me, claims (F80).** The format, in full:155156```157# Team158lead: @vidul159160- @vidul: vidul@ikran.in161 name: Vidul162- @asha: asha@x.com163```164165- **One lead**: the one `lead: @handle` line under `# Team` (a team file without166 it is valid: no lead). Everyone else listed is a member. `team lead @h` sets it167 when there is none, or hands it over when *me* is the lead; `team lead -` clears168 it (the lead only). `team remove` of the lead is refused until it is handed over.169 `team list` marks ` [lead]` and ` (you)`.170- **Me**: `ticket-meta whoami` reads, in order, this session's owner (F92:171 `ticket-meta iam @handle`, asked at session start by grayskull-power's arm,172 kept in git-ignored `.skillator/sessions/<sid>.owner` - line 1 the handle,173 line 2 `session: <id>`, a file naming another session ignored; the sid from174 `SKILLATOR_SESSION`, else Claude Code's session id → `cc-<4-char code>`), then175 `SKILLATOR_ME=@handle`, then this repo's git `user.email` through the team176 emails. A handle not on the team is refused. No match → `not on the team: add177 <email> to .skillator/team.md`.178- **Claims**: planning or dispatching a ticket (relay-morpheus `chain plan` /179 `chain dispatch`, `/pending-sentinel`, `/gauntlet-plan`) runs180 `ticket-meta claim <ID>...` — `[owner: <me>]`, the box kept. A ticket already181 owned by someone else is reassigned (`assign` or `claim`) only by that owner or182 the lead; anyone else is refused, the refusal naming both. Not on the team →183 claims are refused (`add <email> to team.md`).184- **Picking**: `ticket-meta pick [IDs]` prints `you: <me>` then `pick <ID>`185 (unassigned, or mine) or `skip <ID> <owner>` per ticket (no IDs: every `[ ]`186 `[~]` `[!]` ticket). Runs take only the picked; a skipped one is listed as187 skipped with its owner, never run. Not on the team → only unassigned tickets.188 No team file → every ticket is picked and nothing is claimed, as before.189- These checks are a **team convention, not security**: git's email is self-set190 and anyone can edit `team.md` or `TICKETS.md` by hand. They stop honest191 mistakes - two people running one ticket - not a determined teammate.192193**An assignment reopens the ticket.** Whoever it moves to, it must not stay194closed, deferred or in someone else's progress:195196- **"assign F12 to @asha"**, "assign it to asha" → `assign`: sets or replaces197 `[owner: ..]` and the box becomes `[ ]`, from any state.198- **"assign it for a decision to @asha"**, "Asha decides F12" → `decide`: sets or199 replaces `[decide: ..]` and the box becomes `[?]`, from any state.200- **"decided"**, "Asha decided F12" → `decided`: `[?]` back to `[ ]`; the201 `[decide: ..]` tag stays as the record. It refuses a ticket that is not `[?]`.202- The same handle again for the same kind, with the box already `[ ]` (assign)203 or `[?]` (decide), changes nothing and says `no change`; any other box still204 moves.205- Moving a `[~]` ticket keeps its trailing session tag `(@cc-…)` or `(@cc-…:…:…)` beside the new206 `[owner:]`/`[decide:]` — which session works it and who owns it are different207 facts — and warns which session was working it; tell that session its box208 moved. A relay lease is per stage and is released when that stage lands or fails.209- Both refuse a handle not in the team file — say so, and offer to add the210 person there; never invent one.211- `assign` of a ticket someone else owns is refused unless *me* is that owner212 or the lead (F80, above) — say who may, never edit the line by hand around it.213- **`tag <ID>`** when a ticket is closed (`[x]`), and when commits naming it land214 (a merge, a pull). It recomputes `app` and `by` from the commits; with none it215 leaves a hand-set `app` alone.216- **`done`, `block`, `defer`** (F64) set `[x]`, `[!]`, `[>]` from any box but a217 cancelled `[-]`; `block` and `defer` also refuse a done `[x]` (reopen with218 `assign`). `block`/`defer` replace an earlier `(blocked: ..)` or219 `(deferred: ..)` note — the line says only the current wait — and the same220 text again on the same box says `no change`. Tags, other notes and the session221 tag stay; leaving `[~]` warns like `assign`.222- Every edit prints the edited line — that is the read-back. All write under223 `TICKETS.md.lock`, the lock relay-morpheus's `board` flip takes, and refuse224 after 30 s rather than break someone else's.225- Tags go before the trailing `(..)` groups and before a bare `Plan: S<n>`, so226 `check-tickets.sh` still sees that pointer.227228## Allocating an ID229230231Never take "highest on my board + 1" by hand: two worktrees or sessions that do232not share a `TICKETS.md` both get the same number. Run the allocator from the233repo root; it prints the number and reserves it before you write the line:234235```sh236sh "$PRACTICE/scripts/next-id.sh" A # --peek A: look without reserving237```238239`$PRACTICE` is the `practice/` beside the installed skills — resolve it exactly as240`practice/task-loop.md` resolves `taskwork.sh` (Windows: `next-id.ps1 A`,241`-Peek`). It takes 1 + the max of the local board and its archive (done and242archived tickets count — closing never frees a number), both files on every local and remote-tracking ref, and a243counter in the clone's common git dir shared by every worktree, under a lock.244Cross-machine is best-effort: it sees only refs you have fetched, so `git fetch`245first on a shared branch. Sub-parts (`B2a`, `B2b`, …) are the next unused letter246under the parent, by hand — only for genuinely separate pieces.247248**Collision rule:** if two teammates ever land the same number, the later commit249renames its ticket to a fresh number and leaves ` (was B7)` on the line. Never250renumber the earlier one. In a merge, "earlier" is the receiving branch: its IDs251never move; the incoming side's do.252253**The board ships with the work.** `TICKETS.md` (and `TICKETS-archive.md`) is254committed in the same commit as the change it describes and pushed with it —255never held back, never gitignored. A board that stays local is a board the next256clone allocates against blind.257258**Arm the merge guard — once per clone, when this skill arms.** Git hooks and259merge drivers live in `.git/`, not in the repo, so a `git pull` does not bring260them; run this the first time you touch the board in a clone (idempotent —261re-running only refreshes it, so run it every session that arms):262263```sh264sh "$PRACTICE/scripts/renumber-tickets.sh" --install265```266267It copies the script into the clone's common git dir and wires a `tickets` merge268driver for `TICKETS.md` and `TICKETS-archive.md` (two branches that both appended269merge as the union, not a conflict; two edits of one ticket stay a conflict) plus270`post-merge` and `pre-commit` hooks. From then on a plain `git pull` or `git merge`271that brings in an ID the receiving branch already has ends correct with no manual272step: the incoming ticket takes the next free number (archive included) with273` (was F2)`, its sub-parts move with it, references are rewritten only in files274the incoming side changed, and the change lands **in the merge commit**, its275`map:` lines appended to the message and to `.git/skillator/renumber.log`. If276`core.hooksPath` points outside the clone it installs the driver only and says so277— never write into a shared hooks dir. `git pull --rebase` and cherry-pick are278not covered; `merge-smith` runs the same script itself. On a diverged branch a279bare `git pull` stops before merging unless `pull.rebase` is set, so pull with280`--no-rebase` (or `git config pull.rebase false`) for the guard to run.281282A teammate who never runs a skill has no driver and no hooks: their pull either283conflicts on the board or merges both `F2` lines silently. `check-tickets.sh`284below is what catches it, and `renumber-tickets.sh` (inside the merge, before its285commit) is the fix.286287**Detect it at merge time.** Git merges the append-only board by keeping both288sides of an `A43` conflict — the obvious resolution and the wrong one. **After289any merge, rebase, or cherry-pick that touched `TICKETS.md`, and before290committing one:** `sh "$PRACTICE/scripts/check-tickets.sh" TICKETS.md` — name291the board to check another; bare, it checks the current git repo's top-level `TICKETS.md` (`./TICKETS.md` outside git). It fails on292duplicate IDs and committed conflict markers and prints the offending lines. A293clean board is a precondition for allocating, not a nicety.294295## When to log296297- User reports a bug → log a `B` ticket before fixing.298- User asks for a feature/change of any size → log an `F` ticket before building,299 then **invoke `skillator:build-jarvis`** with that ticket. The board logs;300 build-jarvis grades, designs and builds. Never build an `F` ticket inline here.301- **Anything Claude/an agent finds itself → an `A` ticket, if it passes the gate302 below.** A stack trace in a test run, a crash while driving the app, a bug303 spotted during review: log it as pending and keep going. `A` means "nobody304 asked for this, we found it" — it is what keeps discoveries from dying with305 the chat.306307A non-feature one-line edit the user asked for inline (typo, comment, rename,308formatting) needs no ticket and goes direct. A feature of any size is an `F`.309310### The gate — a ticket names a change, not a finding311312A pending line is not cheap. It is a promise to whoever reads the board next,313and a board that grows faster than it drains stops being read at all — at which314point every row on it is worth nothing, including the real ones.315316Before logging, say the change out loud in one sentence: **"someone should edit317X so that Y."** If you can't finish that sentence, it isn't a ticket:318319| What you have | Where it goes |320|---|---|321| A change you can name, that nobody has made | Ticket. |322| Something true about the code that implies no edit | Say it in chat. Nothing to log. |323| A risk with no reproduction and no fix to try | Say it in chat, with what would settle it. Not a ticket. |324| Already fixed in the tree — you just found the fix | Nothing. |325| The same defect as an open row, seen from elsewhere | Nothing; that row already covers it. |326| Work you are about to do in this same turn | Do it. A ticket you close a minute later is noise. |327328An agent's report is **input, not a row.** Reports arrive one per agent, so329converting each into a ticket inflates the board at exactly the rate you spawn330agents. Read the report, apply the gate to every item in it, and log the ones331that pass — normally fewer than were reported. Say in chat what you dropped and332why; that is the audit trail, not a row.333334Two failure modes, both worse than a missing ticket: the same defect logged335three times because three agents saw it, and a row so vague nobody can tell336what "done" would mean. **If you can't write the closing condition, you can't337write the ticket.**338339## Working a ticket340341- Starting → `ticket-meta start <ID>`: `[~]`, an unowned ticket claimed to you (F106), your session tag stamped (F109; a subagent prefixes `SKILLATOR_MODE=agent`), see **Who touched it**.342- Finished *and verified* (tests/build/manual check actually run) → `[x]`,343 via `ticket-meta done <ID> [evidence]`: the box `[x]`, the `tag` a close owes,344 and, when evidence is given, ` **Done <YYYY-MM-DD>: <evidence>**` before the345 session tag (it replaces an earlier Done note). The evidence is one line with346 **no parentheses and no `*`** — ticket-meta refuses them — so write a commit,347 a test result or a quote without them: `RUN-0017 stage 110, bd408c6`, not348 `(RUN-0017, bd408c6)`; `sweep PASS 8/8`, not `**PASS** (8/8)`. It refuses a349 cancelled `[-]` ticket - reopen it with `assign` first.350 Not verified, not done.351- Built, but the verifying test has not run yet and is not yours to run now —352 an owner's live check, a GREEN on another host, a CI run → `[%]` testing,353 via `ticket-meta testing <ID> <what test>`, which writes354 ` (testing: <what test>)` on the line (one line, no parentheses). Testing is355 **open**: report it at session end, and never build on it as if done. It356 leaves only on the result: `ticket-meta tested <ID> pass` → `[x]`,357 `tested <ID> fail` → back to `[~]` to fix; the `(testing: ..)` note stays as358 the record. Not for a test you can run yourself this turn — run it.359- Can't proceed — waiting on someone, a credential, an upstream fix, or another360 ticket → `[!]`, with ` (blocked: <what on>)` on the line, via361 `ticket-meta block <ID> <what on>`. Blocked is still362 **open**: report it at session end, and unblock back to `[ ]` or `[~]` the363 moment the dependency clears. Never leave an agent spinning on a blocked364 ticket — flip it and move to the next one.365- Waiting on a person's decision (which option, whether to do it at all) →366 `[?]` decide, via `ticket-meta decide <ID> @who` so the line names367 who decides. Decide is **open**, like blocked: report it at session368 end, never build it before the decision, and flip it to `[ ]` with369 `ticket-meta decided <ID>` once the answer is in.370- Postponed by choice — not now, waiting on a condition that isn't a hard371 dependency (a later milestone, a build that hasn't run, hardware not on the372 bench) → `[>]`, with ` (deferred: <until what>)` on the line, via373 `ticket-meta defer <ID> <until what>`. Deferred is374 **not open and not closed** — it is off the board until the condition375 arrives: not pending (nobody is picking it up next), not blocked (nobody owes376 you anything), not cancelled (it will be done). Report it at session end as377 its own line, and flip it back to `[ ]` when the condition arrives.378- Dropped — won't fix, obsolete, duplicate, or the user called it off → `[-]`,379 with a short ` — reason` on the line (`[-] B9 — Safari flicker (dup of B4)`).380 Cancelled is a closed state, not a deleted one: the line and its number stay.381- Reference the ID in commit messages: `B3: reject uploads over 5MB` — that382 subject is how `by` and `app` find the work. Closing it → `tag <ID>`383 (**Apps and people**).384- **A board edit is not done until you have read it back.** After every status385 flip, `grep -n '<ID>' TICKETS.md` and report from *that output*, never from the386 edit you believe you made. An edit whose hunk is missing from `git diff` is a387 failed flip, not a done one — silent no-ops are routine here, because388 `TICKETS.md` is UTF-8 and full of em dashes, so any tool that reads it as389 cp1252 (a bare Python `open()` on Windows) matches nothing and changes390 nothing while exiting 0. Read, write and compare it as UTF-8.391- Cycle end / session end: re-read the file and correct any status that drifted,392 then report the open set — every open box: `[ ]`, `[~]`, `[%]`, `[!]` and393 `[?]` — to the user.394- Once the turn's edits are read back, republish the artifact board — see395 **The artifact board**. Board changed, artifact stale, is a bug.396397## Draining the board398399Pending rows are not immortal, and a rising pending count is a symptom to400diagnose — not a backlog to admire. Run a drain **before any handover, release,401or mergeprep-oracle**, and whenever a single session has added more pending rows than402it closed. (Both are checkable on the spot; "has it grown since last time" is403not — no prior count is stored anywhere.) A drain **re-verifies the pending rows404against the tree, not against their own text**:405406- Fix is already in the tree → `[x]`, citing where. Reading the fix is not407 verifying it: `[x]` still means what it means above — run the check. If you408 can only see the code, leave it pending and say the fix looks present.409- No change can be named for it (it was an observation) → `[-] — (not work: <why>)`.410- Same defect as another row → `[-] — (dup of <ID>)`.411- Still real → leave it, and make the line name the change.412413Sweep `[>]` rows in the same pass — that is where stale rows collect, since a414deferred row is off the board until a condition arrives and nothing checks415whether it already has. For each, ask only "has the condition arrived?": yes →416`[ ]`, no → leave it, never going to → `[-]`.417418A row that states its defect confidently is still wrong if a later commit fixed419it, so check the code, never the wording. Rows leave the board only through a420status flip — never by deletion; the archive below moves closed rows, it never421drops one.422423Report the drain as a count: `pending 12 → 5 (3 already fixed, 3 not work, 1 dup)`.424425### Archive what has stayed closed426427A board that keeps every closed row grows until reading it costs more than the428work it tracks. **Archive every time this skill arms** — the first board read of429a session, before reporting the open set — and again at the end of a drain or430release. A step left to "the end of a drain" never runs; this board reached431110 KB that way.432433```sh434sh "$PRACTICE/scripts/archive-tickets.sh" --dry-run # list what would move435sh "$PRACTICE/scripts/archive-tickets.sh" # move it436```437438Moved anything → run `check-tickets.sh`, then commit `TICKETS.md` and439`TICKETS-archive.md` **together, in their own commit** (`tickets: archive N440closed`), and push them with the session's next push. One without the other is441a clone that loses tickets or reuses IDs. Moved nothing → say nothing.442443`[x]` and `[-]` rows closed more than 14 days ago (`--days N`) move to444`TICKETS-archive.md` beside the board, under the same section heading. The445closing date is the commit that flipped the status, read from git — lines carry446no date. A parent stays until it and every sub-part are closed and old enough,447then they move together. The archive is committed with the board and never448edited by hand.449450Sessions read only `TICKETS.md`. The allocator, `check-tickets.sh` and the451artifact board read both files, so an archived number is never reused and a452duplicate across the two still fails. For an old ID the board does not show,453`grep -n '<ID>' TICKETS-archive.md` before saying it does not exist.454455### Sync what is in progress (`/sync-zordon`)456457`[~]` collects rows that are really done, waiting on a test, stuck or parked,458because nothing flips them back; `[!]` and `[ ]` rows go stale the same way. On459`/sync-zordon` (or "sync tickets"), walk **every** `[!]`, `[ ]` and `[~]` row —460or only the IDs given as arguments — and propose the status it really has.461**Propose from evidence, never invent it.**4624630. **Start from `ticket-meta reconcile [IDs]`** (F81, read-only - the ops464 board's `c` key runs the same rule). It prints `ID [now] -> [proposed]465 reason` per row with evidence: a `[!]` whose `(blocked: ..)` names tickets466 all `[x]` → `[ ]`; a check owed by the owner or a team (a `(testing: ..)`467 note, a live check, a release build, a device / rig / hardware, a team to468 confirm) with the code landed → `[%]`; a run stage on it failed, or silent469 a day → `[!]`; landed → `[%]`; a `[ ]` with commits on main led by its ID470 (`F81:`, not `board:` ones) → `[~]`. Landed is the ticket's last run stage471 `x`, or with no stage a commit; a `[!]` still blocked on an open ticket is472 never `[%]`. A row it keeps says "evidence unclear". It never proposes473 `[x]` and skips a `[~]` row with a session tag. Its rows go in the table as474 they are; steps 1-2 add what it cannot see (`[x]`, `[>]`, `[?]`, a `[~]`475 the line shows done).4761. For each `[~]` row read its line and its notes (`Done = ..`, `Progress ..`,477 `Owed ..`, `blocked`, `waiting on`), then `git log --oneline -F --grep=<ID>`478 (keep only subjects naming the ID as a word — `F1` is not `F12`) and any479 practice/baselines file or run file (`.skillator/run-*.md`) the line cites.4802. Propose exactly one:481482 | Proposal | Only when |483 |---|---|484 | `[x]` done | the line's Done criterion is shown met by named evidence — a commit, a test result, an owner confirmation quoted on the line. Cite it, and write it without parentheses or `*` (see step 4). |485 | `[%]` testing | built, and a named test or check is still owed (an owner's live check, another host's GREEN, a CI run) — ` (testing: <what>)` |486 | `[!]` blocked | it cannot proceed until something outside it lands — ` (blocked: <on what>)` |487 | `[>]` deferred | postponed by choice until a condition — ` (deferred: <until what>)` |488 | `[?]` decision | it waits on a person's choice — name who decides |489 | stays `[~]` | still being worked: a session tag on the line (`(@cc-a4f1c9)` or `(@cc-k7q2:asha:run)`, any agent prefix, any shape — reason "worked by @cc-a4f1c9"), a commit naming it in the last 24 hours, or a run stage on it dispatched and not done |490 | stays `[~]`, "evidence unclear" | anything else. Unsure is not done. |491492 A `[~]` row carrying a session tag is held by that session: it stays `[~]`493 ("worked by @cc-xxxx") and is **never** proposed for another status, whatever494 its notes or commits say — unless the user names that ID in the command's495 arguments or in the answer.4964973. Show **one table** — `ID | now -> proposed | reason (the evidence, one line)`498 — then ask **once**: accept all / pick (which IDs) / none. No question tool499 on the host → print the choices as a numbered list and stop.5004. **Apply only the accepted rows, and only on the user's answer.** Headless501 (`claude -p`, a chained or relay stage), or the question comes back502 unanswered → propose only, apply nothing, and say `applied: none (headless)`.503 - `[%]` → `ticket-meta testing <ID> <what test>`.504 - `[?]` → `ticket-meta decide <ID> @who`. With no `.skillator/team.md`505 (decide refuses) do **not** flip the box by hand: leave the row `[~]` and506 say in the report who decides and that `decide` needs a team file. Only if507 the user then asks for it: `ticket-meta team add @who "Name" <email>`508 (it creates the team file), then `decide`.509 - `[x]` → `ticket-meta done <ID> <the evidence>` (it tags the ticket too),510 the evidence written without parentheses or `*`.511 - `[!]` → `ticket-meta block <ID> <on what>`.512 - `[!]` → `[ ]` → `ticket-meta unblock <ID>`; `[ ]` → `[~]` → `ticket-meta start <ID>`.513 - `[>]` → `ticket-meta defer <ID> <until what>`.514 - Never hand-edit a box ticket-meta has a subcommand for.515 - Stamp your session tag on every flipped row (**Who touched it**) - ticket-meta does it when it knows your session.5165. Read the board back — `grep -n '<ID>' TICKETS.md` for every applied ID —517 run `sh "$PRACTICE/scripts/check-tickets.sh"`, and report from that output: `in progress 14 -> 6518 (3 done, 2 testing, 1 blocked, 1 deferred, 1 decision)`.519520### Verify what is in testing (`/verify-shifu`)521522`[%]` says built, a check owed. On `/verify-shifu` (or "verify the testing523tickets"), re-check **every** `[%]` row - or only the IDs given; a named ID not524in `[%]` is reported `not [%]` and skipped - against evidence obtained **now**,525never against the line's own claim.5265271. **One fresh agent per ticket**, no session history, its own prompt: the ID,528 the line verbatim, the repo root. A read-only agent type where the host has529 one; no subagents on the host → check each ticket yourself in turn, same530 rules. The prompt says:531 - Read the line's Done criterion (`Done = ..`, the `(testing: ..)` note) and532 check every part of it: `git log --oneline -F --grep=<ID>` (subjects naming533 the ID as a word), the files and baselines it cites, and **run** the tests534 or checks it names. Evidence is what you saw this run, never a quote of the line.535 - **Read and run tests only** - never edit code, write or delete files in the536 repo, commit, or touch `TICKETS.md`. A check that would need an edit to run537 is not run: FAIL, "needs an edit to check".538 - Answer exactly `VERDICT: PASS|FAIL|OWNER` and `EVIDENCE: <one line>` (no539 parentheses, no `*`), and on FAIL also `WHY: <one line>` - why it failed,540 when you can tell. PASS only when every part is shown met. Anything541 failing, missing or not runnable is FAIL, the EVIDENCE line naming what failed.542 **OWNER** when any part needs the owner's own eyes - `testing: owner ..`, a543 live look, a picker or UI check, an account or credentials, a device - even544 if the rest passed.545 - **`--deep` only** (`/verify-shifu --deep [IDs]`; off by default): after546 the Done check, judge the ticket's code. The commits naming the ID as a547 word, `board:` commits left out, give the range `<oldest>^..<newest>`; run548 code-vader on it (`code-vader.sh collect --range <oldest>^..<newest>`,549 Windows `code-vader.ps1 collect -Range ..`) and its two lenses, charging550 the ticket only for lines its own commits wrote (`git show <sha>` each -551 the range can hold other tickets' commits), plus a design-principles lens: single552 responsibility, coupling and cohesion, naming, error handling at trust553 boundaries, tests that pin behaviour (not internals), `.sh`/`.ps1` twins in554 step. Same severities. PASS only when the Done line is met **and** no555 `critical` or `high` finding; else FAIL, EVIDENCE the top findings (at most556 three, worst first) as `<file:line> - <why>` joined by `; `, reworded557 without parentheses or `*` as ticket-meta needs, no separate WHY (each558 finding carries its own). OWNER still wins.5592. **Record each verdict** in the main session, with ticket-meta only - the560 owner's standing ruling, so no question first, headless included. A verdict561 is a note, never a status: the box stays `[%]` on every verdict (closing it562 stays the owner's `done`). The note replaces any earlier verify note:563 - PASS → `ticket-meta verify <ID> pass <evidence>`:564 ` (verified PASS <date>: <evidence>)` on the line.565 - FAIL → `ticket-meta verify <ID> fail <what failed> - <why>` (` - <why>`566 only when the agent gave a WHY): ` (verified FAIL <date>: <what> - <why>)`.567 - OWNER → nothing. No note.568 - An agent that returns no verdict line is FAIL, "no verdict"; never PASS.5693. Read the board back - `grep -n '<ID>' TICKETS.md` per ticket - run570 `sh "$PRACTICE/scripts/check-tickets.sh"`, and report one table571 `ID | verdict | evidence` and the count: `testing 3 (1 pass, 1 fail, 1 owner)`.572573## Work tickets in parallel, not in a line574575**An `F` ticket is built by `skillator:build-jarvis`, never here.** Before any576edit for one — logged a minute ago, picked from the board, or named in a577headless "work these tickets" — invoke build-jarvis with its id and title. Its578grade line is that ticket's tiering, its phases are the dispatch. **Several579`F` tickets are ONE build-jarvis pass**, one task block per ticket — never one580build-jarvis per ticket. "One agent per ticket" below means, for an `F`, that581ticket's build seat is one dispatched agent inside that pass: it gets the pass's582grade and its own task block, and implements only that (no regrade, no verify of583its own, never build-jarvis loaded as an orchestrator). "It is only a few lines"584is the grade's call (a `—` design seat, a cheap build), not a reason to skip it.585`B` and `A` tickets stay on this page's dispatch below.586587Flipping a ticket to `[~]` means **dispatch an agent for it**, one agent per588ticket, all in a single message so they run concurrently (for `F` tickets,589build-jarvis's Phase 2 does that dispatch). Never work a queue of tickets590serially in the main session — that is the linear development this skill exists591to break.592593- Give each agent its ticket ID, the one-line title, and the repo context it594 needs; tell it to report back what it changed and whether it verified (an F595 build seat: which of its task's tests it ran - the verify seat is not its).596- **Name a model for every dispatch — never let it inherit the session's, and597 grade the tier per ticket, not once for the batch.** Same table as workflow598 mode's scout (below); a mechanical fix and the agent judging it warrant599 different tiers, and so do two tickets in the same message.600- Only the main session edits `TICKETS.md` — agents report, you flip statuses.601 Two agents writing the same file is how you lose tickets.602- Tickets touching the same files are the one exception: run those sequentially,603 or hand the whole cluster to one agent, and say so.604- Sub-parts (`B2a`, `B2b`) are the unit to parallelise when a ticket is big.605606## Workflow mode — working the board in one call607608Dynamic workflows let you write a script that orchestrates many agents609deterministically: real control flow, structured results, a resumable run. Same610board as plain dispatch, scripted.611612**Ask the mode once before a sweep.** When this cycle has 4+ open tickets to613work, or the tickets are a sweep, settle how they run before the first `[~]`614flip or dispatch:615616| Mode | What runs | Fits |617|---|---|---|618| **single** | One dispatched agent works the cycle's tickets in order — never the main session | Tightly coupled tickets, tickets sharing files |619| **per-task** | Plain dispatch: one agent per ticket, all in one message (above); same-file tickets stay one item | Independent tickets — the usual pick when nothing else fits |620| **workflow** | The script in "The shape" below; no `Workflow` tool → the host's parallel delegate, never claimed as a `Workflow` call | 4+ independent tickets or a sweep — costs the most tokens |621622A sweep reached through relay-morpheus also offers **marathon** (its623`references/marathon.md`): the staged form of workflow that keeps going across624sessions.625626Ask once: all three modes, your recommendation first (`AskUserQuestion`; no627such tool → a numbered list). Then **end your turn** — no `[~]` flip, no628dispatch, until the user answers. No question when the user already named a629mode ("ultracode", "use a workflow", "fan out agents", "one agent per ticket",630"single agent") — use it. No question when the mode was already answered this631turn (by the user, or by relay-morpheus's `references/marathon.md` entry) —632don't re-ask. No question when the run is headless, chained or inside a relay —633take your recommendation, capped at per-task unless the user named workflow,634and log `Ruling: mode <m> - <why> - <cost if wrong>`. Unasked, the most you635pick is per-task.636637**`F` tickets in the sweep still go to ONE build-jarvis pass**, handed the638sweep's answer as a named mode, so the user is asked once.639640**Recommend workflow when any of these hold:**641642- **4+ open tickets** to work in this cycle (real fan-out).643- The tickets are a sweep — the same change across N files, an audit, a codemod.644- You want each fix **adversarially verified** before flipping it to `[x]`.645- The user asked: **"ultracode"**, "use a workflow", "fan out646 agents", "orchestrate this with subagents".647648**Stay with plain dispatch when:** 1-3 tickets (no question — per-task, as649today), tickets needing your judgement between them, or a host with no650`Workflow` tool. Off `claude-code`, workflow mode651is a *pattern* — emulate it with the host's parallel delegate mechanism and don't652claim a `Workflow` call happened. See `WORKFLOW.md` beside the installed skills653for the host table.654655**Never start a workflow the user didn't opt into.** A workflow can spawn dozens656of agents; if the board is big and they didn't ask, say what it would cost first.657658**Several workflows in a row, each starting the next with a usage hold** —659"work every open ticket in staged workflows, keep going" — is `relay-morpheus` →660`references/chain.md`; the board rules on this page do not change there.661662### The shape663664Scout inline first — read `TICKETS.md`, pick the tickets for this cycle, group665same-file tickets into one item, **and tier each one** — then pass that list as666`args` and let the script fan out. `pipeline()` is the default: ticket B is being667verified while ticket C is still being fixed.668669#### Tier every ticket during the scout670671A flat `model:` across the fan-out is the expensive mistake this section exists672to prevent: it pays deep-tier price for one-line fixes, or hands a contract673change to a cheap model that burns 3× the turns and fails anyway. **The scout674assigns a tier per ticket per seat** — you have already read the ticket, so675grading it costs nothing extra — and the script reads that off the item.676677Grade the *fix* seat from the ticket's own text, using `PRACTICE.md` §4 and678`practice/task-loop.md` — the same table, applied per ticket:679680| The ticket reads like | fix | verify |681|---|---|---|682| One file, mechanical, the change is named in the ticket | cheap | build |683| 1-2 files, complete spec, nothing to decide | cheap | build |684| Several files, integration or a shared contract | build | build |685| Cause unknown, design judgement, or "sweep every X" | deep | deep |686| Concurrency, auth, money, or a contract others depend on | build | **deep** |687688…(truncated)