team-toon-tack 2.1.0 → 2.3.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,19 @@
+{
+	"name": "ttt-marketplace",
+	"owner": {
+		"name": "wayne930242",
+		"email": "wayne930242@gmail.com"
+	},
+	"metadata": {
+		"description": "Linear task management tools for Claude Code - efficient workflow without MCP overhead",
+		"version": "1.0.0"
+	},
+	"plugins": [
+		{
+			"name": "team-toon-tack",
+			"source": "./",
+			"description": "Linear task sync & management CLI with commands and skills",
+			"version": "2.3.0"
+		}
+	]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,18 @@
+{
+	"name": "team-toon-tack",
+	"description": "Linear task sync & management CLI for Claude Code - saves tokens vs MCP",
+	"version": "2.3.0",
+	"author": {
+		"name": "wayne930242",
+		"email": "wayne930242@gmail.com"
+	},
+	"repository": "https://github.com/wayne930242/team-toon-tack",
+	"license": "MIT",
+	"keywords": [
+		"claude-code",
+		"linear",
+		"task-management",
+		"workflow",
+		"productivity"
+	]
+}

package/README.md

@@ -14,7 +14,7 @@ Optimized Linear workflow for Claude Code — saves significant tokens compared
 - **QA Team Support** — Auto-update parent issues in QA team to "Testing" when completing dev tasks
 - **Attachment Download** — Auto-download Linear images and files to local `.ttt/output/` for AI vision analysis
 - **Blocked Status** — Set tasks as blocked when waiting on external dependencies
-- **Auto Command Setup** — `ttt init` can install Claude Code commands with custom prefix
+- **Claude Code Plugin** — Install plugin for `/ttt-*` commands and auto-activated skills
 - **Cycle History** — Local `.toon` files preserve cycle data for AI context
 - **User Filtering** — Only see issues assigned to you or unassigned
 
@@ -36,7 +36,6 @@ During init, you'll configure:
 - **QA team(s)**: For cross-team parent issue updates, each with its own testing status (optional)
 - **Completion mode**: How task completion is handled (see below)
 - **Status source**: `remote` (update Linear immediately) or `local` (work offline, sync with `ttt sync --update`)
-- **Claude Code commands**: Auto-install with optional prefix (e.g., `/ttt:work-on`)
 
 ### Completion Modes
 
@@ -47,17 +46,30 @@ During init, you'll configure:
 | `upstream_strict` | Mark task as Done + parent to Testing. Falls back to dev testing if no parent. Default when QA team configured. |
 | `upstream_not_strict` | Mark task as Done + parent to Testing. No fallback if no parent. |
 
-### 2. Daily Workflow
+### 2. Install Claude Code Plugin (Optional)
 
-In Claude Code:
+```
+/plugin marketplace add wayne930242/team-toon-tack
+/plugin install team-toon-tack@wayne930242
+```
+
+### 3. Daily Workflow
+
+In Claude Code (with plugin installed):
 
 ```
-/sync              # Fetch all Linear issues for current cycle
-/work-on next      # Pick highest priority task & start working
-/done-job          # Complete task with AI-generated summary
+/ttt-sync              # Fetch all Linear issues for current cycle
+/ttt-work-on next      # Pick highest priority task & start working
+/ttt-done              # Complete task with AI-generated summary
 ```
 
-That's it.
+Or using CLI directly:
+
+```bash
+ttt sync
+ttt work-on next
+ttt done -m "Completed the task"
+```
 
 ---
 
@@ -116,6 +128,15 @@ ttt status MP-123 --set done    # Mark as done
 ttt status MP-123 --set blocked # Set as blocked (waiting on dependency)
 ```
 
+### `ttt get-issue`
+
+Fetch and display issue details from Linear.
+
+```bash
+ttt get-issue MP-123           # Fetch from Linear and display
+ttt get-issue MP-123 --local   # Show from local data only
+```
+
 ### `ttt config`
 
 Configure settings.
@@ -147,6 +168,29 @@ your-project/
 | `LINEAR_API_KEY` | **Required.** Your Linear API key |
 | `TOON_DIR` | Config directory (default: `.ttt`) |
 
+## Claude Code Plugin
+
+Install the plugin for Claude Code integration:
+
+```
+/plugin marketplace add wayne930242/team-toon-tack
+/plugin install team-toon-tack@wayne930242
+```
+
+### Available Commands
+
+| Command | Description |
+|---------|-------------|
+| `/ttt-sync` | Sync Linear issues to local cycle data |
+| `/ttt-work-on` | Start working on a task |
+| `/ttt-done` | Mark current task as completed |
+| `/ttt-status` | Show or modify task status |
+| `/ttt-get-issue` | Fetch and display issue details |
+
+### Auto-Activated Skill
+
+The plugin includes a `linear-task-manager` skill that automatically activates when working with Linear tasks, providing workflow guidance and best practices.
+
 ## License
 
 MIT

package/README.zh-TW.md

@@ -14,7 +14,7 @@
 - **QA 團隊支援** — 完成開發任務時自動將 QA 團隊的 parent issue 更新為「Testing」
 - **附件下載** — 自動下載 Linear 圖片和檔案到本地 `.ttt/output/`，供 AI 視覺分析
 - **阻塞狀態** — 等待外部依賴時可設定任務為 blocked
-- **自動安裝指令** — `ttt init` 可自動安裝 Claude Code commands，支援自訂前綴
+- **Claude Code Plugin** — 安裝 plugin 即可使用 `/ttt-*` 指令和自動啟用的技能
 - **Cycle 歷史保存** — 本地 `.toon` 檔案保留 cycle 資料，方便 AI 檢閱
 - **使用者過濾** — 只顯示指派給你或未指派的工作
 
@@ -36,7 +36,6 @@ ttt init
 - **QA 團隊**：跨團隊 parent issue 更新，各自設定 testing 狀態（可選）
 - **完成模式**：任務完成時的處理方式（見下方說明）
 - **狀態來源**：`remote`（即時更新 Linear）或 `local`（離線工作，用 `ttt sync --update` 同步）
-- **Claude Code commands**：自動安裝，可選前綴（如 `/ttt:work-on`）
 
 ### 完成模式
 
@@ -47,17 +46,30 @@ ttt init
 | `upstream_strict` | 任務標記為 Done，parent 移動到 Testing。若無 parent，fallback 到開發團隊的 testing 狀態。設定 QA 團隊時的預設值。 |
 | `upstream_not_strict` | 任務標記為 Done，parent 移動到 Testing。若無 parent 不做 fallback。 |
 
-### 2. 每日工作流
+### 2. 安裝 Claude Code Plugin（選擇性）
 
-在 Claude Code 中：
+```
+/plugin marketplace add wayne930242/team-toon-tack
+/plugin install team-toon-tack@wayne930242
+```
+
+### 3. 每日工作流
+
+在 Claude Code 中（安裝 plugin 後）：
 
 ```
-/sync              # 從 Linear 取得當前 cycle 所有 issue
-/work-on next      # 挑選最高優先級任務並開始工作
-/done-job          # 完成任務，附上 AI 生成的摘要
+/ttt-sync              # 從 Linear 取得當前 cycle 所有 issue
+/ttt-work-on next      # 挑選最高優先級任務並開始工作
+/ttt-done              # 完成任務，附上 AI 生成的摘要
 ```
 
-就這樣。
+或直接使用 CLI：
+
+```bash
+ttt sync
+ttt work-on next
+ttt done -m "完成任務"
+```
 
 ---
 
@@ -116,6 +128,15 @@ ttt status MP-123 --set done    # 標記為完成
 ttt status MP-123 --set blocked # 設為阻塞（等待外部依賴）
 ```
 
+### `ttt get-issue`
+
+從 Linear 取得並顯示 issue 詳細資訊。
+
+```bash
+ttt get-issue MP-123           # 從 Linear 取得並顯示
+ttt get-issue MP-123 --local   # 只從本地資料顯示
+```
+
 ### `ttt config`
 
 配置設定。
@@ -147,6 +168,29 @@ your-project/
 | `LINEAR_API_KEY` | **必填**。你的 Linear API 金鑰 |
 | `TOON_DIR` | 配置目錄（預設：`.ttt`） |
 
+## Claude Code Plugin
+
+安裝 plugin 以整合 Claude Code：
+
+```
+/plugin marketplace add wayne930242/team-toon-tack
+/plugin install team-toon-tack@wayne930242
+```
+
+### 可用指令
+
+| 指令 | 說明 |
+|------|------|
+| `/ttt-sync` | 同步 Linear issue 到本地 |
+| `/ttt-work-on` | 開始處理任務 |
+| `/ttt-done` | 標記當前任務完成 |
+| `/ttt-status` | 顯示或修改任務狀態 |
+| `/ttt-get-issue` | 取得並顯示 issue 詳情 |
+
+### 自動啟用技能
+
+Plugin 包含 `linear-task-manager` 技能，在處理 Linear 任務時會自動啟用，提供工作流程指導和最佳實踐。
+
 ## 授權
 
 MIT

package/commands/ttt-done.md

@@ -0,0 +1,62 @@
+---
+name: ttt-done
+description: Mark current task as completed
+arguments:
+  - name: issue-id
+    description: Optional issue ID if multiple tasks in progress
+    required: false
+  - name: message
+    description: Completion message (use -m flag)
+    required: false
+---
+
+# TTT Done Command
+
+Mark the current in-progress task as completed.
+
+## Usage
+
+### Auto-Select (single in-progress task)
+```bash
+ttt done
+```
+
+### Specific Issue
+If `issue-id` is provided:
+```bash
+ttt done {{ issue-id }}
+```
+
+### With Completion Message
+If `message` is provided:
+```bash
+ttt done -m "{{ message }}"
+```
+
+### Combined
+```bash
+ttt done {{ issue-id }} -m "{{ message }}"
+```
+
+## What This Does
+
+Based on configured completion mode:
+
+| Mode | Behavior |
+|------|----------|
+| `simple` | Task → Done, Parent → Done |
+| `strict_review` | Task → Testing, Parent → QA Testing |
+| `upstream_strict` | Task → Done, Parent → Testing |
+| `upstream_not_strict` | Task → Done, Parent → Testing (no fallback) |
+
+Also:
+1. Gets latest git commit info
+2. Adds completion comment to Linear with commit details
+3. Syncs task back from Linear to update local status
+
+## Before Running
+
+Ensure you have:
+1. Committed your changes with a meaningful message
+2. Run tests and lint checks
+3. Pushed to remote branch (if applicable)

package/commands/ttt-get-issue.md

@@ -0,0 +1,71 @@
+---
+name: ttt-get-issue
+description: Fetch and display issue details from Linear
+arguments:
+  - name: issue-id
+    description: Issue ID to fetch (e.g., MP-624)
+    required: true
+  - name: local
+    description: Only show from local data (add --local flag)
+    required: false
+---
+
+# TTT Get-Issue Command
+
+Fetch and display full issue details from Linear.
+
+## Usage
+
+### Fetch from Linear
+```bash
+ttt get-issue {{ issue-id }}
+```
+
+### Show from Local Data Only
+If `local` is "true" or "--local":
+```bash
+ttt get-issue {{ issue-id }} --local
+```
+
+## What This Does
+
+1. Fetches full issue details from Linear API (or local cache if --local)
+2. Displays comprehensive information:
+   - Title and description
+   - Status (both Linear and local)
+   - Priority level
+   - Labels
+   - Assignee
+   - Branch name
+   - Parent issue (if subtask)
+   - Attachments with local paths
+   - Comments with timestamps
+
+## Use Cases
+
+- Review issue details before starting work
+- Check requirements and acceptance criteria
+- View attachments and mockups
+- Read comment history and discussions
+- Verify issue status without full sync
+
+## Output Format
+
+```
+📋 MP-624: Issue Title
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Status: In Progress | Local: in-progress
+Priority: 🔴 Urgent
+Labels: frontend, bug
+Assignee: developer@example.com
+Branch: feature/mp-624-fix-bug
+
+Description:
+[Full description content]
+
+Attachments:
+- screenshot.png (local: .ttt/output/MP-624/...)
+
+Comments:
+[Comment history]
+```

package/commands/ttt-status.md

@@ -0,0 +1,65 @@
+---
+name: ttt-status
+description: Show or modify task status
+arguments:
+  - name: issue-id
+    description: Issue ID to check/modify (omit for current in-progress task)
+    required: false
+  - name: set
+    description: New status to set (+1, -1, pending, in-progress, completed, blocked, done)
+    required: false
+---
+
+# TTT Status Command
+
+Show or modify the status of a task.
+
+## Usage
+
+### Show Current In-Progress Task
+```bash
+ttt status
+```
+
+### Show Specific Issue
+If `issue-id` is provided:
+```bash
+ttt status {{ issue-id }}
+```
+
+### Set Status
+If `set` is provided:
+```bash
+ttt status {{ issue-id }} --set {{ set }}
+```
+
+## Status Values
+
+| Value | Description |
+|-------|-------------|
+| `+1` | Move to next status (pending → in-progress → completed) |
+| `-1` | Move to previous status |
+| `+2` | Skip two statuses forward |
+| `-2` | Skip two statuses backward |
+| `pending` | Set to pending |
+| `in-progress` | Set to in-progress |
+| `completed` | Set to completed |
+| `blocked` | Set to blocked (waiting on dependency) |
+| `todo` | Set Linear to Todo status |
+| `done` | Set Linear to Done status |
+
+## Examples
+
+```bash
+ttt status MP-624 --set +1       # Move to next status
+ttt status MP-624 --set blocked  # Mark as blocked
+ttt status --set pending         # Reset current task
+```
+
+## Output
+
+Displays:
+- Task ID and title
+- Local status vs Linear status
+- Priority and labels
+- Assignee information

package/commands/ttt-sync.md

@@ -0,0 +1,51 @@
+---
+name: ttt-sync
+description: Sync Linear issues to local cycle data
+arguments:
+  - name: issue-id
+    description: Optional specific issue ID to sync (e.g., MP-624)
+    required: false
+  - name: update
+    description: Push local status changes to Linear (add --update flag)
+    required: false
+---
+
+# TTT Sync Command
+
+Sync issues from Linear to local `.ttt/cycle.toon` file.
+
+## Usage
+
+Run the sync command based on arguments provided:
+
+### Default Sync (all matching issues)
+```bash
+ttt sync
+```
+
+### Sync Specific Issue
+If `issue-id` is provided:
+```bash
+ttt sync {{ issue-id }}
+```
+
+### Push Local Changes
+If `update` is "true" or "--update":
+```bash
+ttt sync --update
+```
+
+## What This Does
+
+1. Fetches active cycle from Linear
+2. Downloads all issues matching configured filters (team, status, labels)
+3. Preserves local status for existing tasks
+4. Downloads Linear images to `.ttt/output/`
+5. Updates `cycle.toon` with fresh data
+
+## Output
+
+After running, report:
+- Number of tasks synced
+- Current cycle name
+- Any status updates pushed to Linear (if --update used)

package/commands/ttt-work-on.md

@@ -0,0 +1,48 @@
+---
+name: ttt-work-on
+description: Start working on a Linear task
+arguments:
+  - name: issue-id
+    description: Issue ID (e.g., MP-624), 'next' for auto-select, or omit for interactive
+    required: false
+---
+
+# TTT Work-On Command
+
+Start working on a task from the current cycle.
+
+## Usage
+
+### Interactive Selection
+```bash
+ttt work-on
+```
+
+### Specific Issue
+If `issue-id` is provided (e.g., MP-624):
+```bash
+ttt work-on {{ issue-id }}
+```
+
+### Auto-Select Highest Priority
+If `issue-id` is "next":
+```bash
+ttt work-on next
+```
+
+## What This Does
+
+1. Marks the task as `in-progress` locally
+2. Updates Linear status to "In Progress" (if status_source is remote)
+3. Displays full task details including:
+   - Title and description
+   - Priority and labels
+   - Attachments and comments
+   - Branch name for checkout
+
+## After Running
+
+1. Read the task description and requirements
+2. Check out the suggested branch: `git checkout -b <branch-name>`
+3. Run type-check and lint before starting: `bun type-check && bun lint`
+4. Begin implementation

package/dist/bin/cli.js

@@ -12,6 +12,7 @@ const COMMANDS = [
     "work-on",
     "done",
     "status",
+    "get-issue",
     "config",
     "help",
     "version",
@@ -24,14 +25,15 @@ USAGE:
   ttt <command> [options]
 
 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)
-  done      Mark current task as completed
-  status    Show or modify task status
-  config    Configure settings (status mappings, filters)
-  help      Show this help message
-  version   Show version
+  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)
+  done       Mark current task as completed
+  status     Show or modify task status
+  get-issue  Fetch and display issue details from Linear
+  config     Configure settings (status mappings, filters)
+  help       Show this help message
+  version    Show version
 
 GLOBAL OPTIONS:
   -d, --dir <path>    Config directory (default: .ttt)
@@ -46,6 +48,7 @@ EXAMPLES:
   ttt work-on next              # Auto-select highest priority
   ttt done                      # Complete current task
   ttt done -m "Fixed the bug"   # With completion message
+  ttt get-issue MP-123          # Fetch issue details from Linear
 
 ENVIRONMENT:
   LINEAR_API_KEY    Required. Your Linear API key
@@ -117,6 +120,10 @@ async function main() {
                 process.argv = ["node", "status.js", ...commandArgs];
                 await import(`${scriptDir}status.js`);
                 break;
+            case "get-issue":
+                process.argv = ["node", "get-issue.js", ...commandArgs];
+                await import(`${scriptDir}get-issue.js`);
+                break;
             case "config":
                 process.argv = ["node", "config.js", ...commandArgs];
                 await import(`${scriptDir}config.js`);

package/dist/scripts/config/teams.js

@@ -1,6 +1,6 @@
 import prompts from "prompts";
-import { getLinearClient, saveLocalConfig, } from "../utils.js";
 import { getDefaultStatusTransitions } from "../lib/config-builder.js";
+import { getLinearClient, saveLocalConfig, } from "../utils.js";
 export async function configureTeams(_config, localConfig) {
     console.log("👥 Configure Teams\n");
     const client = getLinearClient();

package/dist/scripts/get-issue.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/scripts/get-issue.js

@@ -0,0 +1,61 @@
+import { displayTaskFull } from "./lib/display.js";
+import { fetchIssueDetail } from "./lib/sync.js";
+import { loadCycleData } from "./utils.js";
+async function getIssue() {
+    const args = process.argv.slice(2);
+    if (args.includes("--help") || args.includes("-h")) {
+        console.log(`Usage: ttt get-issue <issue-id> [--local]
+
+Fetch and display issue details from Linear.
+
+Arguments:
+  issue-id    Issue ID (e.g., MP-624). Required.
+
+Options:
+  --local     Only show from local cycle data, don't fetch from Linear
+
+Examples:
+  ttt get-issue MP-624         # Fetch from Linear and display
+  ttt get-issue MP-624 --local # Show from local data only`);
+        process.exit(0);
+    }
+    const localOnly = args.includes("--local");
+    const issueId = args.find((arg) => !arg.startsWith("-"));
+    if (!issueId) {
+        console.error("Issue ID is required.");
+        console.error("Usage: ttt get-issue <issue-id>");
+        process.exit(1);
+    }
+    // If local only, get from cycle data
+    if (localOnly) {
+        const data = await loadCycleData();
+        if (!data) {
+            console.error("No cycle data found. Run ttt sync first.");
+            process.exit(1);
+        }
+        const task = data.tasks.find((t) => t.id === issueId || t.id === `MP-${issueId}`);
+        if (!task) {
+            console.error(`Issue ${issueId} not found in local data.`);
+            process.exit(1);
+        }
+        displayTaskFull(task, "📋");
+        return;
+    }
+    // Fetch from Linear
+    console.log(`Fetching ${issueId} from Linear...`);
+    const task = await fetchIssueDetail(issueId);
+    if (!task) {
+        console.error(`Issue ${issueId} not found in Linear.`);
+        process.exit(1);
+    }
+    // Check local data for local status
+    const data = await loadCycleData();
+    if (data) {
+        const localTask = data.tasks.find((t) => t.id === issueId);
+        if (localTask) {
+            task.localStatus = localTask.localStatus;
+        }
+    }
+    displayTaskFull(task, "📋");
+}
+getIssue().catch(console.error);