toga-ai 1.0.33 → 1.0.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.33",
+  "version": "1.0.35",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",

package/skills/kickoff/SKILL.md

@@ -112,15 +112,45 @@ Ask these in one message. **Present the repos/projects you already know** (read
 
 1. **Framework** — 1.0, 2.0, or **both**?
 2. **Layer** — front-end, back-end, or hybrid?
-3. **Repo / project** — list the registered repos for the chosen framework(s) as options
-   (show `repo` and `project`), plus **"a new repo not listed"**. If they pick the new-repo
-   option, run **New-repo onboarding** (below) before continuing.
-4. **Client** — which client is this for, or "shared / internal"? (List `clients/` folders
-   you know of, plus "a new client".)
+3. **Repo(s) / project(s)** — **list EVERY registered repo for the chosen framework(s)** —
+   do not abbreviate or show only a few. **This is a multi-select (checkbox), not a single
+   choice;** a session often spans more than one repo/project, so always let the developer
+   pick several. If they pick a repo not listed, run **New-repo onboarding** (below) for
+   each new repo before continuing.
+4. **Client** — which client is this for, or "shared / internal"? **List EVERY folder under
+   `knowledge/clients/`** plus "shared / internal" and "a new client" — do not show only a
+   subset.
 5. **What are you building or changing?** (a sentence — used to pick relevant feature docs.)
 
 If any answer is unclear, ask again. Do not guess the framework, repo, project, or client.
 
+### How to present the repo and client choices (questions 3 and 4)
+
+**Do NOT use the option-chip / radio question control for questions 3 and 4.** That
+control caps at ~4 options, which silently truncates the list — with 7+ repos or 3+
+clients the developer never sees the full set. Instead, **render the full list as a
+numbered markdown list in a normal message** and ask the developer to reply with the
+numbers they want (e.g. "1, 3, 5"). This shows every repo and every client with no cap
+and naturally supports multi-select.
+
+```
+**Which repo(s)/project(s)?** (reply with the numbers, multiple OK)
+  1. _underscore  (_Underscore — 2.0 core)
+  2. worker2      (Worker — 2.0 app)
+  3. api2         (API — 2.0 app)
+  ... every registered repo for the chosen framework(s) ...
+  N. a new repo not listed
+
+**Which client?** (one, or "shared / internal")
+  1. compass-canada
+  2. compass-usa
+  ... every folder under knowledge/clients/ ...
+  S. shared / internal
+  X. a new client
+```
+
+Framework (q1) and layer (q2) have ≤4 options, so the chip control is fine for those.
+
 ## Step 3 — Resolve the repos this work needs (local paths, lazily)
 
 Compute the load set with `node "<TEAM_REPO>/knowledge.js" deps --repo=<chosen-repo>`