team-toon-tack 3.9.0 → 3.9.3

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.9.1"
 		}
 	]
 }

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.9.1",
 	"author": {
 		"name": "wayne930242",
 		"email": "wayne930242@gmail.com"

package/.codex-plugin/plugin.json

@@ -0,0 +1,20 @@
+{
+	"name": "team-toon-tack",
+	"version": "3.9.1",
+	"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

@@ -67,9 +67,32 @@ 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):
@@ -237,7 +260,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
@@ -253,7 +276,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

@@ -67,9 +67,32 @@ 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 後）：
@@ -237,7 +260,7 @@ your-project/
 
 ```
 /plugin marketplace add wayne930242/team-toon-tack
-/plugin install team-toon-tack@wayne930242
+/plugin install team-toon-tack@ttt-marketplace
 ```
 
 ### 可用指令
@@ -253,7 +276,7 @@ your-project/
 
 ### 自動啟用技能
 
-Plugin 包含 `linear-task-manager` 技能，在處理任務時會自動啟用，提供工作流程指導和最佳實踐。
+Plugin 包含 `managing-linear-tasks` 技能，在處理任務時會自動啟用，提供工作流程指導和最佳實踐。
 
 ## 授權
 

package/commands/ttt-work-on.md

@@ -5,7 +5,6 @@ arguments:
   - name: issue-id
     description: "Issue ID (e.g., MP-624) or 'next' for auto-select. Defaults to 'next'."
     required: false
-    default: next
   - name: dry-run
     description: Preview selection without changing status
     required: false
@@ -48,67 +47,21 @@ Options:
   --dry-run   Pick task without changing status (preview only)
 ```
 
-## Workflow — Plan → Test → Code → Review
+## After Selection — Delegate the Implementation
 
-Follow this loop for every task.
-Skipping phases is not "pragmatic", it is debt.
+This command picks the task. The implementation workflow belongs to the user.
 
-### 1. Branch
+**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.
 
-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.
+**Only when none exists**, run this minimal loop:
 
-```bash
-git checkout -b <branch-name-matching-user-convention>
-```
-
-### 2. Plan
-
-Scope decides depth.
-
-- 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.
-
-Never go straight to code.
-Planning collapses ambiguity before implementation.
-
-### 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"
-```
-
-A task is NOT complete until `/ttt:done` runs.
-This is MANDATORY.
-
-## 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.
+Either path closes the task with `/ttt:done -m "summary"`.
 
 ## Error Handling
 

package/dist/bin/cli.js

@@ -172,7 +172,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);
+});

package/dist/scripts/create.d.ts

@@ -1,2 +1,2 @@
 #!/usr/bin/env bun
-export {};
+export declare function create(args?: string[]): Promise<void>;

package/dist/scripts/create.js

@@ -1,4 +1,6 @@
 #!/usr/bin/env bun
+import path from "node:path";
+import { pathToFileURL } from "node:url";
 import { input, select } from "@inquirer/prompts";
 import { createAdapter } from "./lib/adapters/index.js";
 import { getSourceType, getTeamId, loadConfig, loadCycleData, loadLocalConfig, sourceIssueToTask, upsertTaskInCycleData, } from "./utils.js";
@@ -121,8 +123,7 @@ async function resolveParentSourceId(adapter, parentIdentifier) {
     }
     return parent.sourceId;
 }
-async function create() {
-    const args = process.argv.slice(2);
+export async function create(args = process.argv.slice(2)) {
     if (args.includes("--help") || args.includes("-h")) {
         console.log(`Usage: ttt create [options]
 
@@ -156,6 +157,10 @@ Examples:
     const labelArg = parsed.label;
     const statusName = parsed.status;
     const parentId = parsed.parent;
+    if (sourceType === "trello" && parentId) {
+        console.error("Parent issues are not supported for Trello cards.");
+        process.exit(1);
+    }
     if (!title) {
         if (!parsed.interactive) {
             console.error("Title is required when --no-interactive is set.");
@@ -204,8 +209,13 @@ Examples:
     }
     console.log("Creating issue...");
     const adapter = createAdapter(config);
+    let cycleData = sourceType === "trello" ? await loadCycleData() : null;
+    if (sourceType === "trello" && !cycleData) {
+        console.error("No cycle data found. Run ttt sync before creating a card.");
+        process.exit(1);
+    }
     const assigneeId = resolveAssigneeId(config, assigneeKey);
-    const statusId = await resolveStatusId(config, adapter, teamId, statusName);
+    const statusId = await resolveStatusId(config, adapter, teamId, sourceType === "trello" && !statusName ? "todo" : statusName);
     const labelIds = resolveLabelIds(config, labelArg);
     const parentSourceId = await resolveParentSourceId(adapter, parentId);
     const currentCycle = await adapter.getCurrentCycle(teamId);
@@ -229,11 +239,19 @@ Examples:
     console.log(`\n✅ Created ${issue.id}: ${issue.title}`);
     if (issue.url)
         console.log(`   ${issue.url}`);
-    const cycleData = await loadCycleData();
+    if (sourceType !== "trello")
+        cycleData = await loadCycleData();
     if (cycleData) {
         const task = sourceIssueToTask(issue, sourceType);
         await upsertTaskInCycleData(task, cycleData);
         console.log(`   Added to local cycle data.`);
     }
 }
-create().catch(console.error);
+const entryPath = process.argv[1];
+if (entryPath &&
+    import.meta.url === pathToFileURL(path.resolve(entryPath)).href) {
+    create().catch((error) => {
+        console.error("Failed to create issue:", error instanceof Error ? error.message : error);
+        process.exitCode = 1;
+    });
+}

package/dist/scripts/lib/adapters/linear-adapter.js

@@ -294,18 +294,25 @@ export class LinearAdapter {
     }
     async cancelIssue(sourceId) {
         try {
-            // Find the "Cancelled" workflow state for this issue's team
+            // Resolve by statusType, not display name -- teams name this state
+            // "Canceled", "Cancelled", "Done - Cancelled", etc.
             const issue = await this.client.issue(sourceId);
             const team = await issue.team;
             if (!team) {
                 return { success: false, error: "Could not determine issue team" };
             }
             const states = await this.client.workflowStates({
-                filter: { team: { id: { eq: team.id } }, type: { eq: "cancelled" } },
+                filter: {
+                    team: { id: { eq: team.id } },
+                    type: { in: ["canceled", "cancelled"] },
+                },
             });
             const cancelledState = states.nodes[0];
             if (!cancelledState) {
-                return { success: false, error: "No 'cancelled' workflow state found" };
+                return {
+                    success: false,
+                    error: `No cancelled-type workflow state found for team ${team.id}`,
+                };
             }
             const payload = await this.client.updateIssue(sourceId, {
                 stateId: cancelledState.id,

package/dist/scripts/lib/adapters/trello-adapter.d.ts

@@ -27,7 +27,7 @@ export declare class TrelloAdapter implements TaskSourceAdapter {
         error?: string;
     }>;
     getInitData(teamId?: string): Promise<InitData>;
-    createIssue(_options: CreateIssueOptions): Promise<{
+    createIssue(options: CreateIssueOptions): Promise<{
         success: boolean;
         issue?: SourceIssue;
         error?: string;

package/dist/scripts/lib/adapters/trello-adapter.js

@@ -4,6 +4,12 @@
  */
 import { TrelloClient } from "../trello.js";
 import { detectPriorityFromLabels, } from "./types.js";
+const PRIORITY_NAMES = {
+    1: "urgent",
+    2: "high",
+    3: "medium",
+    4: "low",
+};
 export class TrelloAdapter {
     type = "trello";
     client;
@@ -278,11 +284,85 @@ export class TrelloAdapter {
             currentCycle: undefined, // Trello has no cycle
         };
     }
-    async createIssue(_options) {
-        return {
-            success: false,
-            error: "createIssue is not yet supported for Trello",
-        };
+    async createIssue(options) {
+        try {
+            const statuses = await this.getStatuses(options.teamId);
+            const targetStatus = options.statusId
+                ? statuses.find((status) => status.id === options.statusId)
+                : statuses[0];
+            if (!targetStatus) {
+                return {
+                    success: false,
+                    error: options.statusId
+                        ? `Trello list ${options.statusId} is not open on board ${options.teamId}`
+                        : `Trello board ${options.teamId} has no open lists`,
+                };
+            }
+            const labelIds = new Set(options.labelIds ?? []);
+            let knownLabels = [];
+            if (labelIds.size > 0 || (options.priority ?? 0) > 0) {
+                knownLabels = await this.getLabels(options.teamId);
+            }
+            if (options.priority && options.priority > 0) {
+                const priorityLabel = knownLabels.find((label) => detectPriorityFromLabels([label.name]) === options.priority);
+                if (!priorityLabel) {
+                    return {
+                        success: false,
+                        error: `Trello board ${options.teamId} has no label matching priority "${PRIORITY_NAMES[options.priority]}"`,
+                    };
+                }
+                labelIds.add(priorityLabel.id);
+            }
+            const card = await this.client.createCard({
+                name: options.title,
+                idList: targetStatus.id,
+                desc: options.description,
+                idMembers: options.assigneeId ? [options.assigneeId] : undefined,
+                idLabels: labelIds.size > 0 ? [...labelIds] : undefined,
+            });
+            if (!card.id || !card.shortLink || !card.name || !card.idList) {
+                return {
+                    success: false,
+                    error: "Trello created a card but returned an incomplete response",
+                };
+            }
+            const labelNames = Array.isArray(card.labels)
+                ? card.labels.map((label) => label.name).filter(Boolean)
+                : knownLabels
+                    .filter((label) => labelIds.has(label.id))
+                    .map((label) => label.name);
+            const status = statuses.find((candidate) => candidate.id === card.idList)?.name ??
+                targetStatus.name;
+            const assigneeId = Array.isArray(card.idMembers)
+                ? card.idMembers[0]
+                : options.assigneeId;
+            return {
+                success: true,
+                issue: {
+                    id: card.shortLink,
+                    sourceId: card.id,
+                    title: card.name,
+                    description: card.desc || undefined,
+                    status,
+                    statusId: card.idList,
+                    assigneeId,
+                    assigneeEmail: undefined,
+                    priority: detectPriorityFromLabels(labelNames),
+                    labels: labelNames,
+                    url: card.url,
+                    parentIssueId: undefined,
+                    branchName: undefined,
+                    attachments: undefined,
+                    comments: undefined,
+                },
+            };
+        }
+        catch (error) {
+            return {
+                success: false,
+                error: error instanceof Error ? error.message : "Unknown error",
+            };
+        }
     }
     async updateIssue(_sourceId, _fields) {
         return {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "team-toon-tack",
-	"version": "3.9.0",
+	"version": "3.9.3",
 	"description": "Linear & Trello task sync & management CLI with TOON format",
 	"type": "module",
 	"bin": {
@@ -14,6 +14,7 @@
 	"files": [
 		"dist",
 		".claude-plugin",
+		".codex-plugin",
 		"commands",
 		"skills"
 	],

package/skills/managing-linear-tasks/SKILL.md

@@ -3,12 +3,13 @@ name: managing-linear-tasks
 description: Use when the user mentions Linear or Trello issues, references issue IDs like MP-123, or asks to sync, show, start, complete, create, assign, edit, cancel, comment on, or check status of tasks.
 ---
 
-<law>
-ALL task operations MUST go through the `ttt` CLI via Bash tool.
-NEVER manually edit `.ttt/` files (cycle.toon, config.toon, local.toon).
-NEVER fabricate issue data — always run the CLI to get real data.
-After completing any task, MUST execute `/ttt:done -m "summary"`.
-</law>
+## 執行方式
+
+在 Codex 與 Claude Code 中，使用可用的 shell 工具執行 `ttt` CLI。
+任務資料以 CLI 的查詢結果為準；透過 CLI 更新 `.ttt/` 內的設定與狀態。
+使用者要求完成任務時，執行 `ttt done -m "摘要"`。
+Claude Code 也提供 `/ttt:*` slash commands，對應下方相同的 CLI 操作。
+
 
 # Task Manager (Linear/Trello)
 
@@ -16,23 +17,23 @@ Manage developer task workflows using the `ttt` CLI.
 
 ## Command Router
 
-Match user intent to the correct `/ttt:*` command:
+依使用者意圖選擇下列 `ttt` CLI 指令：
 
 | User Intent | Command | Example |
 |-------------|---------|---------|
-| Sync/fetch issues | `/ttt:sync` | "sync my issues", "pull from Linear" |
-| Show/search issues | `/ttt:show` | "show MP-624", "list my tasks", "what issues do I have" |
-| Start working on a task | `/ttt:work-on` | "work on next", "start MP-624" |
-| Create a new issue | `/ttt:create` | "create issue", "open a ticket", "new task" |
-| Reassign an issue | `/ttt:assign` | "assign MP-624 to john", "reassign to jane" |
-| Edit issue fields | `/ttt:edit` | "rename MP-624", "change priority", "update labels" |
-| Cancel an issue | `/ttt:cancel` | "cancel MP-624", "abandon this task" |
-| Record an estimate | `/ttt:estimate` | "estimate MP-624 as 6h", "save 2.5h estimate" |
-| Check/change status | `/ttt:status` | "what's my current task", "set MP-624 to blocked" |
-| Add a comment | `/ttt:comment` | "comment on MP-624", "add note to task" |
-| Complete a task | `/ttt:done` | "done", "mark complete", "finish task" |
-
-**When a matching intent is detected, invoke the corresponding `/ttt:*` slash command.**
+| Sync/fetch issues | `ttt sync` | "sync my issues", "pull from Linear" |
+| Show/search issues | `ttt show` | "show MP-624", "list my tasks", "what issues do I have" |
+| Start working on a task | `ttt work-on` | "work on next", "start MP-624" |
+| Create a new issue | `ttt create` | "create issue", "open a ticket", "new task" |
+| Reassign an issue | `ttt assign` | "assign MP-624 to john", "reassign to jane" |
+| Edit issue fields | `ttt edit` | "rename MP-624", "change priority", "update labels" |
+| Cancel an issue | `ttt cancel` | "cancel MP-624", "abandon this task" |
+| Record an estimate | `ttt estimate` | "estimate MP-624 as 6h", "save 2.5h estimate" |
+| Check/change status | `ttt status` | "what's my current task", "set MP-624 to blocked" |
+| Add a comment | `ttt comment` | "comment on MP-624", "add note to task" |
+| Complete a task | `ttt done` | "done", "mark complete", "finish task" |
+
+**意圖符合時，透過 shell 工具執行對應的 `ttt` CLI 指令。**
 
 ## Quick Reference
 
@@ -96,7 +97,7 @@ ttt sync → ttt work-on next → ttt estimate <id> <hours> → [implement] →
 | "I'll edit `cycle.toon` directly, faster" | `cycle.toon` is auto-generated. Manual edits get overwritten on next `ttt sync`. Always go through the CLI. |
 | "I remember this issue ID, no need to sync" | Remote status, assignee, priority may have changed. Run `ttt sync` or `ttt show <id> --remote` first. |
 | "I'll create the issue in the Linear/Trello UI instead" | Bypassing `ttt create` leaves the new issue outside local cycle data. Use the CLI so it gets tracked. |
-| "Task is obvious, skip `/ttt:done`" | `/ttt:done` syncs local + remote status, posts a completion comment, reads git commit info. Skipping leaves state inconsistent. |
+| "Task is obvious, skip `ttt done`" | `ttt done` syncs local + remote status, posts a completion comment, reads git commit info. Skipping leaves state inconsistent. |
 | "I know what the task needs without reading it" | Fabricated assumptions produce wrong work. Run `ttt show <id>` before starting. |
 | "Fetch issue details via Linear MCP / web UI" | The CLI is authoritative and token-efficient. Use `ttt show` / `ttt sync`, not alternate data paths. |
 
@@ -109,17 +110,17 @@ digraph ttt_router {
     user [label="User mentions\nLinear/Trello", shape=doublecircle];
     classify [label="Classify intent", shape=diamond];
 
-    sync     [label="/ttt:sync",    shape=box];
-    show     [label="/ttt:show",    shape=box];
-    work_on  [label="/ttt:work-on", shape=box];
-    create   [label="/ttt:create",  shape=box];
-    assign   [label="/ttt:assign",  shape=box];
-    edit     [label="/ttt:edit",    shape=box];
-    cancel   [label="/ttt:cancel",  shape=box];
-    estimate [label="/ttt:estimate", shape=box];
-    status   [label="/ttt:status",  shape=box];
-    comment  [label="/ttt:comment", shape=box];
-    done     [label="/ttt:done",    shape=box];
+    sync     [label="ttt sync",    shape=box];
+    show     [label="ttt show",    shape=box];
+    work_on  [label="ttt work-on", shape=box];
+    create   [label="ttt create",  shape=box];
+    assign   [label="ttt assign",  shape=box];
+    edit     [label="ttt edit",    shape=box];
+    cancel   [label="ttt cancel",  shape=box];
+    estimate [label="ttt estimate", shape=box];
+    status   [label="ttt status",  shape=box];
+    comment  [label="ttt comment", shape=box];
+    done     [label="ttt done",    shape=box];
 
     user -> classify;
     classify -> sync     [label="fetch / pull"];