Make the parking lot Wave X, and record two tea label traps #27
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/milestones-are-ordering-and-tea-label-traps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three corrections to
/issue-triage, all found by recategorising a real tracker(someones.computer, 2026-08-15) rather than by re-reading the skill.
Deferred work goes to
Wave X, not the last numberNumbering the parking lot reads fine until the backlog earns another wave — then everything
added afterwards appears to come after the deferred bucket. That is exactly what happened:
Wave 4: Deferred and gatedhad to becomeWave Xso three new waves could append withoutimplying they came last.
Xnever collides, so the numbered waves stay a contiguous run.A milestone is an ordering, never a subject
An issue gets exactly one milestone, so a topic-milestone buys the topic visibility by
spending the issue's place in the queue. A third of that tracker (39 issues) sat in a
Managed servicesmilestone, outside every wave, while--fields labelssaid nothing aboutwhat those issues even were.
Subject belongs on a label, where it costs nothing and stacks — an issue is then both what
it is about and when it happens. So a cluster big enough to feel like it deserves its own
milestone is the signal to give it a label and split it across waves by dependency. The
retirement turned one bucket into three waves plus a label hierarchy.
-Ltakes a comma list but is not repeatable-L "bug,observability"applies both;-L bug -L observabilityapplies only the last one,silently, exit 0. The skill already warned that
-Ladds rather than replaces — it did notwarn about this, and the failure looks identical to success.
Adds the labels API as the bulk form, plus one more trap:
tea apiexpands{owner}/{repo}from
$PWD, so running it from a scratch directory returns a bare404 page not foundonstdout, which surfaces downstream as a parse error rather than as "wrong directory".
Verification
Docs-only — the entire repo is Markdown and this diff is one
.mdfile, so per VCS.md thisopens ready rather than draft. markdownlint-cli2 reports an identical 76 findings before and
after (all pre-existing MD060 on table separator rows), so the change introduces none.
The consuming repo's copy of this skill was updated in parallel with the concrete tables this
one deliberately keeps illustrative.
Three corrections to /issue-triage, all found by recategorising a real tracker (someones.computer, 2026-08-15) rather than by reading the skill. - **Deferred work goes to `Wave X`.** Numbering it last reads fine until the backlog earns another wave, and then everything added afterwards appears to come after the parking lot. X never collides, so the numbered waves stay contiguous and new ones append without a renumber. - **A milestone is an ordering, never a subject.** An issue gets exactly one milestone, so a topic-milestone buys the topic visibility by spending the issue's place in the queue. A third of that tracker sat in a `Managed services` milestone, outside every wave, while `--fields labels` said nothing about what those issues were. Subject belongs on a label, where it costs nothing and stacks; a cluster big enough to want its own milestone is a cluster that wants a label and a split across waves. - **`-L` takes a comma list but is not repeatable.** `-L a -L b` applies only `b`, silently, exit 0. Adds the labels API as the bulk form, and notes that `tea api` expands {owner}/{repo} from $PWD — run it from a scratch directory and every call returns a bare 404 on stdout, which surfaces downstream as a parse error rather than as a wrong-directory message.