team-toon-tack 3.9.0 → 3.10.0

package/.claude-plugin/marketplace.json

@@ -13,7 +13,7 @@
 			"name": "team-toon-tack",
 			"source": "./",
 			"description": "Linear/Trello task sync & management CLI with commands and skills",
-			"version": "2.8.5"
+			"version": "3.10.0"
 		}
 	]
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
 	"name": "team-toon-tack",
 	"description": "Linear/Trello task sync & management CLI for Claude Code - saves tokens vs MCP",
-	"version": "2.8.5",
+	"version": "3.10.0",
 	"author": {
 		"name": "wayne930242",
 		"email": "wayne930242@gmail.com"

package/.codex-plugin/plugin.json

@@ -0,0 +1,20 @@
+{
+	"name": "team-toon-tack",
+	"version": "3.10.0",
+	"description": "透過 ttt CLI 同步與管理 Linear、Trello 任務。",
+	"author": {
+		"name": "wayne930242"
+	},
+	"repository": "https://github.com/wayne930242/team-toon-tack",
+	"license": "MIT",
+	"skills": "./skills/",
+	"interface": {
+		"displayName": "team-toon-tack",
+		"shortDescription": "同步與管理 Linear、Trello 任務",
+		"longDescription": "透過 ttt CLI 同步任務、查詢狀態、記錄估時，並依使用者要求更新 Linear 與 Trello。",
+		"developerName": "wayne930242",
+		"category": "Productivity",
+		"capabilities": ["Interactive", "Write"],
+		"defaultPrompt": ["使用 ttt 同步並列出我的任務。"]
+	}
+}

package/README.md

@@ -8,7 +8,7 @@ Optimized task workflow for Claude Code — supports Linear and Trello, saves si
 
 - **Token Efficient** — Local cycle cache eliminates repeated API calls, saving significant tokens vs MCP
 - **Multi-source Support** — Works with both Linear and Trello
-- **Smart Task Selection** — Auto-pick your highest priority pending task with `/work-on next`
+- **Batch Ticket Claiming** — Claim one or many tickets at once with `ttt claim`, or auto-pick your highest priority pending tasks with `ttt claim next <n>`
 - **Multi-team Support** — Sync and filter issues across multiple teams/boards
 - **Flexible Sync Modes** — Choose between remote (immediate sync) or local (offline-first, sync later with `--update`)
 - **Completion Modes** — Four modes for task completion (Linear): simple, strict review, upstream strict, upstream not strict
@@ -67,16 +67,39 @@ During init, you'll be prompted to select your task source (Linear or Trello) an
 
 ```
 /plugin marketplace add wayne930242/team-toon-tack
-/plugin install team-toon-tack@wayne930242
+/plugin install team-toon-tack@ttt-marketplace
 ```
 
+### Codex plugin 安裝（選擇性）
+
+先依上方步驟安裝 `ttt` CLI 並執行 `ttt init`。Plugin 提供任務管理技能，透過 shell 呼叫 CLI。
+
+從 GitHub 安裝：
+
+```bash
+codex plugin marketplace add wayne930242/team-toon-tack
+codex plugin add team-toon-tack@ttt-marketplace
+```
+
+從本地 checkout 安裝，在此 repository 根目錄執行：
+
+```bash
+codex plugin marketplace add "$PWD"
+codex plugin add team-toon-tack@ttt-marketplace
+```
+
+若已註冊同名的 GitHub marketplace，先執行 `codex plugin marketplace remove ttt-marketplace`，再加入本地路徑。
+修改已安裝的同版本內容後，先執行 `codex plugin remove team-toon-tack@ttt-marketplace`，再執行上述 `codex plugin add` 重新安裝。
+
+安裝完成後開啟新的 Codex 對話，使用 `$managing-linear-tasks`，或直接說「使用 ttt 同步並列出我的任務」。Codex 會使用 `ttt sync`、`ttt show` 等 CLI 指令。
+
 ### 3. Daily Workflow
 
 In Claude Code (with plugin installed):
 
 ```
 /ttt:sync              # Fetch all issues/cards for current cycle
-/ttt:work-on next      # Pick highest priority task & start working
+/ttt:work-on next      # Claim highest priority ticket & start working
 /ttt:estimate MP-123 6 # Save a local 6-hour estimate
 /ttt:done              # Complete task with AI-generated summary
 ```
@@ -85,7 +108,7 @@ Or using CLI directly:
 
 ```bash
 ttt sync
-ttt work-on next
+ttt claim next
 ttt estimate MP-123 6
 ttt done -m "Completed the task"
 ```
@@ -121,16 +144,23 @@ ttt sync MP-123       # Sync specific issue only
 ttt sync --update     # Push local status changes to remote (for local mode)
 ```
 
-### `ttt work-on`
+### `ttt claim`
 
-Start working on a task.
+Claim ticket(s): move them to in-progress locally and on the remote source.
+Alias: `ttt work-on`.
 
 ```bash
-ttt work-on              # Interactive selection
-ttt work-on MP-123       # Specific issue
-ttt work-on next         # Auto-select highest priority
+ttt claim                  # Interactive multi-select
+ttt claim MP-123           # Claim one ticket
+ttt claim MP-123 MP-124    # Batch claim
+ttt claim next             # Claim highest priority pending task
+ttt claim next 3           # Claim top 3 pending tasks
+ttt claim --dry-run        # Preview without changes
 ```
 
+Completed, in-review, and blocked tickets are reported and skipped without
+stopping the rest of the batch. An unknown ID aborts before anything is claimed.
+
 ### `ttt estimate`
 
 Save a local human-effort estimate that persists in `.ttt/cycle.toon`.
@@ -237,7 +267,7 @@ Install the plugin for Claude Code integration:
 
 ```
 /plugin marketplace add wayne930242/team-toon-tack
-/plugin install team-toon-tack@wayne930242
+/plugin install team-toon-tack@ttt-marketplace
 ```
 
 ### Available Commands
@@ -245,7 +275,7 @@ Install the plugin for Claude Code integration:
 | Command | Description |
 |---------|-------------|
 | `/ttt:sync` | Sync issues to local cycle data |
-| `/ttt:work-on` | Start working on a task |
+| `/ttt:work-on` | Claim ticket(s) and work on them |
 | `/ttt:estimate` | Save a local human-effort estimate |
 | `/ttt:done` | Mark current task as completed |
 | `/ttt:status` | Show or modify task status |
@@ -253,7 +283,7 @@ Install the plugin for Claude Code integration:
 
 ### Auto-Activated Skill
 
-The plugin includes a `linear-task-manager` skill that automatically activates when working with tasks, providing workflow guidance and best practices.
+The plugin includes a `managing-linear-tasks` skill that automatically activates when working with tasks, providing workflow guidance and best practices.
 
 ## License
 

package/README.zh-TW.md

@@ -8,7 +8,7 @@
 
 - **節省 Token** — 本地 cycle 快取避免重複 API 呼叫，比 MCP 省下大量 token
 - **多來源支援** — 支援 Linear 和 Trello
-- **智慧任務挑選** — `/work-on next` 自動選擇指派給你的最高優先級待辦任務
+- **批次領票** — `ttt claim` 可一次領一張或多張票，`ttt claim next <n>` 自動領取最高優先級的待辦任務
 - **多團隊支援** — 跨多個團隊/看板同步與過濾 issue
 - **彈性同步模式** — 選擇 remote（即時同步）或 local（離線優先，稍後用 `--update` 同步）
 - **完成模式** — 四種任務完成模式（Linear）：簡單、嚴格審查、上下游嚴格、上下游非嚴格
@@ -67,16 +67,39 @@ ttt init
 
 ```
 /plugin marketplace add wayne930242/team-toon-tack
-/plugin install team-toon-tack@wayne930242
+/plugin install team-toon-tack@ttt-marketplace
 ```
 
+### Codex plugin 安裝（選擇性）
+
+先依上方步驟安裝 `ttt` CLI 並執行 `ttt init`。Plugin 提供任務管理技能，透過 shell 呼叫 CLI。
+
+從 GitHub 安裝：
+
+```bash
+codex plugin marketplace add wayne930242/team-toon-tack
+codex plugin add team-toon-tack@ttt-marketplace
+```
+
+從本地 checkout 安裝，在此 repository 根目錄執行：
+
+```bash
+codex plugin marketplace add "$PWD"
+codex plugin add team-toon-tack@ttt-marketplace
+```
+
+若已註冊同名的 GitHub marketplace，先執行 `codex plugin marketplace remove ttt-marketplace`，再加入本地路徑。
+修改已安裝的同版本內容後，先執行 `codex plugin remove team-toon-tack@ttt-marketplace`，再執行上述 `codex plugin add` 重新安裝。
+
+安裝完成後開啟新的 Codex 對話，使用 `$managing-linear-tasks`，或直接說「使用 ttt 同步並列出我的任務」。Codex 會使用 `ttt sync`、`ttt show` 等 CLI 指令。
+
 ### 3. 每日工作流
 
 在 Claude Code 中（安裝 plugin 後）：
 
 ```
 /ttt:sync              # 取得當前 cycle 所有 issue/card
-/ttt:work-on next      # 挑選最高優先級任務並開始工作
+/ttt:work-on next      # 領取最高優先級的票並開始工作
 /ttt:estimate MP-123 6 # 寫入本地 6 小時估時
 /ttt:done              # 完成任務，附上 AI 生成的摘要
 ```
@@ -85,7 +108,7 @@ ttt init
 
 ```bash
 ttt sync
-ttt work-on next
+ttt claim next
 ttt estimate MP-123 6
 ttt done -m "完成任務"
 ```
@@ -121,16 +144,23 @@ ttt sync MP-123       # 只同步特定 issue
 ttt sync --update     # 將本地狀態推送到遠端（local 模式用）
 ```
 
-### `ttt work-on`
+### `ttt claim`
 
-開始處理任務。
+領票：把票在本地與遠端來源改成 in-progress。
+別名：`ttt work-on`。
 
 ```bash
-ttt work-on              # 互動選擇
-ttt work-on MP-123       # 指定 issue
-ttt work-on next         # 自動選擇最高優先級
+ttt claim                  # 互動多選
+ttt claim MP-123           # 領一張票
+ttt claim MP-123 MP-124    # 批次領票
+ttt claim next             # 領最高優先級的待辦任務
+ttt claim next 3           # 領最高優先級的前 3 張票
+ttt claim --dry-run        # 預覽，不改狀態
 ```
 
+已完成、審核中、blocked 的票會逐張回報並跳過，不中斷整批。
+批次中出現不存在的 ID 時，整批在動任何票之前中止。
+
 ### `ttt estimate`
 
 把人類工程工時估算寫進 `.ttt/cycle.toon`，並在之後的同步中保留下來。
@@ -237,7 +267,7 @@ your-project/
 
 ```
 /plugin marketplace add wayne930242/team-toon-tack
-/plugin install team-toon-tack@wayne930242
+/plugin install team-toon-tack@ttt-marketplace
 ```
 
 ### 可用指令
@@ -245,7 +275,7 @@ your-project/
 | 指令 | 說明 |
 |------|------|
 | `/ttt:sync` | 同步 issue 到本地 |
-| `/ttt:work-on` | 開始處理任務 |
+| `/ttt:work-on` | 領票並開始處理 |
 | `/ttt:estimate` | 寫入本地人力估時 |
 | `/ttt:done` | 標記當前任務完成 |
 | `/ttt:status` | 顯示或修改任務狀態 |
@@ -253,7 +283,7 @@ your-project/
 
 ### 自動啟用技能
 
-Plugin 包含 `linear-task-manager` 技能，在處理任務時會自動啟用，提供工作流程指導和最佳實踐。
+Plugin 包含 `managing-linear-tasks` 技能，在處理任務時會自動啟用，提供工作流程指導和最佳實踐。
 
 ## 授權
 

package/commands/ttt-comment.md

@@ -57,5 +57,5 @@ Report:
 | Error | Solution |
 |-------|----------|
 | `Message is required` | Add `-m "your message"` |
-| `No in-progress task` | Specify issue-id or run `ttt work-on` first |
+| `No in-progress task` | Specify issue-id or run `ttt claim` first |
 | `Issue not found` | Issue doesn't exist in remote either — check the ID |

package/commands/ttt-status.md

@@ -80,5 +80,5 @@ If a `--set` operation is performed, the remote task is added to local cycle dat
 
 | Error | Solution |
 |-------|----------|
-| `No in-progress task` | Specify issue-id or run `ttt work-on` first |
+| `No in-progress task` | Specify issue-id or run `ttt claim` first |
 | `Issue not found` | Issue doesn't exist in remote either — check the ID |

package/commands/ttt-work-on.md

@@ -1,114 +1,82 @@
 ---
 name: ttt:work-on
-description: Start working on a Linear task
+description: Claim Linear/Trello ticket(s) and work on them
 arguments:
-  - name: issue-id
-    description: "Issue ID (e.g., MP-624) or 'next' for auto-select. Defaults to 'next'."
+  - name: issue-ids
+    description: "One or more issue IDs (e.g., MP-624 MP-625), or 'next' / 'next <n>' for auto-select. Defaults to 'next'."
     required: false
-    default: next
   - name: dry-run
     description: Preview selection without changing status
     required: false
 ---
 
 <law>
-YOU MUST execute the `ttt work-on` command using the Bash tool.
+YOU MUST execute the `ttt claim` command using the Bash tool.
 DO NOT manually edit cycle.toon or change task status by other means.
-After the task is completed, YOU MUST execute `/ttt:done -m "summary"`. This is MANDATORY.
+After each task is completed, YOU MUST execute `/ttt:done -m "summary"`. This is MANDATORY.
 </law>
 
-# /ttt:work-on — Start Working on a Task
+# /ttt:work-on — Claim a Ticket and Work on It
+
+`ttt claim` is the command; `ttt work-on` is its alias. Claiming moves the ticket
+to in-progress locally and on the remote source.
 
 ## Execution
 
 ```bash
-ttt work-on {{ issue-id | default: "next" }} {{ "--dry-run" if dry-run }}
+ttt claim {{ issue-ids | default: "next" }} {{ "--dry-run" if dry-run }}
 ```
 
 ### Argument Resolution
 
 | Input | Command |
 |-------|---------|
-| (none) | `ttt work-on next` |
-| `next` | `ttt work-on next` |
-| `MP-624` | `ttt work-on MP-624` |
-| `--dry-run` | `ttt work-on next --dry-run` |
-| `MP-624 --dry-run` | `ttt work-on MP-624 --dry-run` |
+| (none) | `ttt claim next` |
+| `next` | `ttt claim next` |
+| `next 3` | `ttt claim next 3` |
+| `MP-624` | `ttt claim MP-624` |
+| `MP-624 MP-625` | `ttt claim MP-624 MP-625` |
+| `--dry-run` | `ttt claim next --dry-run` |
+| `MP-624 --dry-run` | `ttt claim MP-624 --dry-run` |
 
 ## Full CLI Reference
 
 ```
-Usage: ttt work-on [issue-id] [options]
+Usage: ttt claim [issue-id...] [options]
+
+Claim ticket(s): move them to in-progress locally and on the remote source.
+Alias: ttt work-on
 
 Arguments:
-  issue-id    Issue ID (e.g., MP-624) or 'next' for auto-select
-              If omitted, shows interactive selection
+  issue-id    One or more issue IDs (e.g., MP-624 MP-625)
+              'next' claims the highest priority pending task
+              'next <n>' claims the top <n> pending tasks
+              If omitted, shows interactive multi-select
 
 Options:
-  --dry-run   Pick task without changing status (preview only)
-```
-
-## Workflow — Plan → Test → Code → Review
-
-Follow this loop for every task.
-Skipping phases is not "pragmatic", it is debt.
-
-### 1. Branch
-
-Check current branch and repo convention first (e.g. recent `git log --oneline -10`, existing branch naming pattern).
-If unclear whether to branch or what name to use, ask the user instead of assuming.
-
-```bash
-git checkout -b <branch-name-matching-user-convention>
+  --dry-run   Pick tickets without changing status (preview only)
 ```
 
-### 2. Plan
-
-Scope decides depth.
+Tickets that are already completed, in review, or blocked are reported and
+skipped without stopping the rest of the batch. An unknown ID aborts before
+anything is claimed.
 
-- Unclear requirements or 3+ files touched → if your environment has a brainstorming/planning skill, use it; otherwise clarify scope with the user and write a short plan before coding.
-- Clear and small (≤2 files, obvious change) → state a 2–3 bullet plan inline before coding.
+## After Claiming — Delegate the Implementation
 
-Never go straight to code.
-Planning collapses ambiguity before implementation.
+This command claims the tickets. The implementation workflow belongs to the user.
 
-### 3. Test First (TDD)
-
-Red → Green → Refactor per behavior:
-
-1. Write one failing test naming the behavior.
-2. Run test — verify it fails for the expected reason.
-3. Write minimal code to pass.
-4. Run test — verify pass, other tests still green.
-5. Refactor if needed, keep green.
-
-No production code without a failing test first.
-
-### 4. Review (before `/ttt:done`)
-
-Verify before claiming completion — run and confirm output:
-
-- Full test suite passes.
-- `npm run lint` / `npm run type` clean (or project-specific commands).
-- Only requested scope changed — no drive-by edits.
-- No debug logs, stubs, TODOs.
-
-Evidence before assertions.
-Do not claim complete without running the commands.
-
-### 5. Complete
-
-```text
-/ttt:done -m "summary"
-```
+**Use the user's own workflow whenever one exists** — routing or laws in their root `CLAUDE.md`, the project `CLAUDE.md`, or a `work-on` / `start-work` skill. Follow it as written and add nothing.
 
-A task is NOT complete until `/ttt:done` runs.
-This is MANDATORY.
+**Only when none exists**, run this minimal loop:
 
-## Project-Specific Skill
+- Branch using the repo's existing naming convention.
+- State a short plan before coding; for unclear scope or 3+ files, settle the scope with the user first.
+- Write the failing test first, then the minimal code to pass it.
+- Run lint / type / test and report the real output before claiming completion.
+- Offer `/ttt:write-work-on-skill` to capture this project's commands as a reusable skill.
 
-Check `.claude/skills/work-on/` or `.claude/skills/start-work/` for project-specific lint / type / test commands and conventions.
-If missing, suggest `/ttt:write-work-on-skill` — it scaffolds a skill following this same 4-phase structure.
+When several tickets were claimed at once, carry them one at a time and close
+each with `/ttt:done -m "summary"` before starting the next.
 
 ## Error Handling
 

package/commands/ttt-write-work-on-skill.md

@@ -49,7 +49,7 @@ Create `.claude/skills/{{ $1 | default: "work-on" }}/SKILL.md` using the Plan
 ```markdown
 ---
 name: {{ $1 | default: "work-on" }}
-description: Project workflow — Plan → Test → Code → Review. Invoke after ttt work-on picks a task.
+description: Project workflow — Plan → Test → Code → Review. Invoke after ttt claim claims a ticket.
 ---
 
 # Work-On Skill ({{ project-name }})

package/dist/bin/cli.js

@@ -10,6 +10,7 @@ const VERSION = pkg.version;
 const COMMANDS = [
     "init",
     "sync",
+    "claim",
     "work-on",
     "estimate",
     "done",
@@ -34,7 +35,8 @@ USAGE:
 COMMANDS:
   init       Initialize config files in current directory
   sync       Sync issues from Linear to local cycle.ttt
-  work-on    Start working on a task (interactive or by ID)
+  claim      Claim ticket(s) and move them to in-progress
+  work-on    Alias for claim
   estimate   Store a local human-effort estimate for a task
   done       Mark current task as completed
   status     Show or modify task status
@@ -58,9 +60,9 @@ EXAMPLES:
   ttt init                      # Initialize .ttt directory
   ttt init -d ./custom          # Initialize in custom directory
   ttt sync                      # Sync from Linear
-  ttt work-on                   # Interactive task selection
-  ttt work-on MP-123            # Work on specific issue
-  ttt work-on next              # Auto-select highest priority
+  ttt claim                     # Interactive multi-select
+  ttt claim MP-123 MP-124       # Claim several tickets at once
+  ttt claim next 3              # Claim top 3 pending tasks
   ttt estimate MP-123 6         # Save a 6-hour estimate locally
   ttt done                      # Complete current task
   ttt done -m "Fixed the bug"   # With completion message
@@ -146,9 +148,10 @@ async function main() {
                 process.argv = ["node", "sync.js", ...commandArgs];
                 await importScript("sync.js");
                 break;
+            case "claim":
             case "work-on":
-                process.argv = ["node", "work-on.js", ...commandArgs];
-                await importScript("work-on.js");
+                process.argv = ["node", "claim.js", ...commandArgs];
+                await importScript("claim.js");
                 break;
             case "estimate":
                 process.argv = ["node", "estimate.js", ...commandArgs];
@@ -172,7 +175,7 @@ async function main() {
                 break;
             case "create":
                 process.argv = ["node", "create.js", ...commandArgs];
-                await importScript("create.js");
+                await importScript("create.js").then((module) => module.create());
                 break;
             case "assign":
                 process.argv = ["node", "assign.js", ...commandArgs];

package/dist/scripts/cancel.js

@@ -70,4 +70,7 @@ Examples:
         console.log(`   Removed from local cycle data.`);
     }
 }
-cancel().catch(console.error);
+cancel().catch((error) => {
+    console.error(error);
+    process.exit(1);
+});