From d8379a15bad2fedbb86fe1ce8529e3648cae5b56 Mon Sep 17 00:00:00 2001 From: Brummel Date: Wed, 20 May 2026 15:07:51 +0200 Subject: [PATCH] =?UTF-8?q?workflow:=20retire=20`todo`=20label=20=E2=80=94?= =?UTF-8?q?=20unlabelled=20IS=20the=20default=20bucket?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `todo` and `feature` were semantically near-identical ("do it, no spec needed") and the boss-pickup decision treated both the same. Collapsing the larger one into "no label" cuts the tag-noise on 16 of 24 issues; the 3 `feature` issues retain the label as a deliberate "substantive but no full spec" marker against the unlabelled bucket of mechanical follow-ups. Label `todo` deleted in Gitea (Tea removed it from the 16 issues automatically). Remaining labels: `milestone`, `feature`, `idea`, `in-progress`. In-tree changes: - CLAUDE.md: Gitea-issues bullet describes the new shape — three semantic labels + unlabelled-default-bucket. - skills/boss/SKILL.md: Step 1 filter-snippet and direction- freedom commentary updated. - skills/brainstorm/SKILL.md: Step 7.5 tea-create template drops `todo` from the choice set and notes that omitting `--labels` is the default-bucket path. Verification: cargo test --workspace 647/0/2, architect_sweeps exit 0, zero residual `todo`-as-label refs in live docs. --- CLAUDE.md | 22 ++++++++++++---------- skills/boss/SKILL.md | 13 +++++++------ skills/brainstorm/SKILL.md | 5 ++++- 3 files changed, 23 insertions(+), 17 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 9ebb56c..c0362b7 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -226,16 +226,18 @@ not retroactively renamed. - **Gitea issues** (since 2026-05-20) are the forward queue — milestones, features, todos, and ideas. Browse: http://192.168.178.103:3000/Brummel/AILang/issues. CLI: `tea - issues ls --repo Brummel/AILang`. Labels: `milestone`, - `feature`, `todo`, `idea` (semantic class) and `in-progress` - (work has started). Big chunks that get their own - `docs/specs/` entry live as Gitea **milestones** (containers); - smaller items are standalone issues. No formal priority axis — - "what's next" is an orchestrator judgement call per session, - not a pre-set label. `idea` is the "may be cut" marker. The - orchestrator owns the backlog: opening new issues, retagging, - closing on completion (typically via the `closes #N` commit- - body trailer). + issues ls --repo Brummel/AILang`. Labels: `milestone` (needs a + `docs/specs/` entry, bounces back to the user in /boss), + `feature` (substantive addition, no full spec), `idea` (may be + cut, no commitment), `in-progress` (work has started). An + unlabelled issue is the default: a concrete task to just do, + no spec needed. Big chunks live as Gitea **milestones** + (containers); smaller items are standalone issues. No formal + priority axis — "what's next" is an orchestrator judgement + call per session, not a pre-set label. The orchestrator owns + the backlog: opening new issues, retagging, closing on + completion (typically via the `closes #N` commit-body + trailer). - **`docs/specs/.md`** (since 2026-05-09): per-milestone design spec produced by `skills/brainstorm`. Hard-gate before any diff --git a/skills/boss/SKILL.md b/skills/boss/SKILL.md index 5aa5460..27e0479 100644 --- a/skills/boss/SKILL.md +++ b/skills/boss/SKILL.md @@ -70,17 +70,18 @@ mode. This skill does not restate them. The Gitea issue backlog is the forward queue. Browse: http://192.168.178.103:3000/Brummel/AILang/issues. CLI: `tea issues ls --repo Brummel/AILang --state open` lists every -open issue; `--labels milestone` / `feature` / `todo` / `idea` -filters by semantic class. Read a candidate body with +open issue; `--labels milestone` / `feature` / `idea` filters by +semantic class. Unlabelled issues are the default "just do it" +bucket. Read a candidate body with `tea issues --repo Brummel/AILang`. There is no formal priority axis (`prio:*` labels were retired 2026-05-20). Pick the next item by orchestrator judgement: typically the simplest in-flight follow-up to the just-closed -milestone, then a `todo` or `feature` that unblocks something, -then `milestone` (which is itself a bounce-back per §"Direction -freedom"). `idea` is "may be cut" and should rarely be picked -autonomously. +milestone, then an unlabelled issue or a `feature` that +unblocks something, then `milestone` (which is itself a +bounce-back per §"Direction freedom"). `idea` is "may be cut" +and should rarely be picked autonomously. If the entire open backlog is empty: skip to Step 5 (done-state). Do not invent work; an empty queue is a real signal that the diff --git a/skills/brainstorm/SKILL.md b/skills/brainstorm/SKILL.md index f495bb3..1626df4 100644 --- a/skills/brainstorm/SKILL.md +++ b/skills/brainstorm/SKILL.md @@ -248,13 +248,16 @@ interpretation: ```bash tea issues create --repo Brummel/AILang \ --title "" \ - --labels "" \ + --labels "" \ --description " **context:** **depends on:** " ``` + (Omit `--labels` entirely for an unlabelled default-bucket + issue.) + 3. Tell the user the spec was retired and which Gitea issue was filed (include the issue number). No commit is needed for the backlog entry — Gitea is the live store.