claude-plugin-viban 1.3.3 → 1.3.5

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "viban",
-  "version": "1.3.3",
+  "version": "1.3.5",
   "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
   "author": {
     "name": "happy-nut"

package/bin/viban

@@ -1526,13 +1526,17 @@ cmd_review() {
 
 cmd_done() {
     init_json
-    [[ -z "$1" ]] && { echo "Usage: viban done <id>"; exit 1; }
+    [[ -z "$1" ]] && { echo "Usage: viban done <id> [--remove]"; exit 1; }
+    local id="$1"
+    local remove=false
+    [[ "$2" == "--remove" ]] && remove=true
+
     # Cleanup worktree if exists
     local repo_root=$(git rev-parse --show-toplevel 2>/dev/null)
-    local wt_dir="$VIBAN_DATA_DIR/worktrees/$1"
+    local wt_dir="$VIBAN_DATA_DIR/worktrees/$id"
 
-    local branch="issue-$1"
-    local _ext_id=$(get_ext_id "$1")
+    local branch="issue-$id"
+    local _ext_id=$(get_ext_id "$id")
     if [[ -n "$_ext_id" && "$_ext_id" != "null" ]]; then
         local _issue_num="${_ext_id##*:}"
         if git -C "$repo_root" rev-parse --verify "issue-${_issue_num}" &>/dev/null 2>&1; then
@@ -1545,14 +1549,22 @@ cmd_done() {
         git -C "$repo_root" branch -D "$branch" 2>/dev/null
         echo "✓ worktree removed"
     fi
-    # Remove task (handle both string and number ID)
-    jq --argjson id "$1" 'del(.issues[]|select((.id|tonumber)==$id))' "$VIBAN_JSON" > "$VIBAN_JSON.tmp" && \
-    mv "$VIBAN_JSON.tmp" "$VIBAN_JSON"
 
-    # Clear iTerm2 session name
-    printf '\033]1;\007'
-
-    echo "✓ $(display_id "$1" "$(get_ext_id "$1")") completed & removed"
+    if $remove; then
+        # Delete card (old behavior)
+        jq --argjson id "$id" 'del(.issues[]|select((.id|tonumber)==$id))' \
+            "$VIBAN_JSON" > "$VIBAN_JSON.tmp" && mv "$VIBAN_JSON.tmp" "$VIBAN_JSON"
+        printf '\033]1;\007'
+        echo "✓ $(display_id "$id" "$(get_ext_id "$id")") completed & removed"
+    else
+        # Move to done status (non-destructive default)
+        local now=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+        jq --argjson id "$id" --arg now "$now" \
+            '(.issues[]|select((.id|tonumber)==$id)) |= . + {status:"done",assigned_to:null,updated_at:$now}' \
+            "$VIBAN_JSON" > "$VIBAN_JSON.tmp" && mv "$VIBAN_JSON.tmp" "$VIBAN_JSON"
+        printf '\033]1;\007'
+        echo "✓ $(display_id "$id" "$(get_ext_id "$id")") → done"
+    fi
 }
 
 cmd_get() { init_json; jq --argjson id "$1" '.issues[]|select((.id|tonumber)==$id)' "$VIBAN_JSON"; }
@@ -1673,7 +1685,7 @@ main() {
         attach) shift; cmd_attach "$@";;
         assign) cmd_assign "$2";;
         review) cmd_review "$2";;
-        done)   cmd_done "$2";;
+        done)   cmd_done "$2" "$3";;
         get)    cmd_get "$2";;
         edit)   [[ -z "$2" ]] && { echo "Usage: viban edit <id>"; exit 1; }; edit_issue "$2";;
         priority) cmd_priority "$2" "$3";;
@@ -1706,7 +1718,7 @@ main() {
             echo "  viban priority <id> <P0-P3>   Set priority"
             echo "  viban assign      Assign first backlog (by priority)"
             echo "  viban review      → Human Review"
-            echo "  viban done <id>   Complete & remove"
+            echo "  viban done <id> [--remove]   Complete (--remove to delete)"
             echo "  viban edit <id>   Edit task in editor"
             echo "  viban get <id>    Get task details (JSON)"
             echo "  viban migrate     Migrate: extract type from title"

package/commands/add.md

@@ -2,6 +2,8 @@
 description: "Register a problem as a viban issue"
 ---
 
+> Tip: Run `/clear` before `/viban:add` for a clean context.
+
 # /add - Register Issue
 
 Register a problem as a viban issue. No codebase exploration, no solutions — symptoms only.
@@ -40,17 +42,20 @@ Infer from description. Don't ask unless truly ambiguous.
 ## Step 4: Register
 
 ```bash
-cat > /tmp/viban-desc.md <<'VIBAN_EOF'
+mkdir -p .viban/tmp
+cat > .viban/tmp/desc.md <<'VIBAN_EOF'
 ## Symptoms
 {one-sentence symptom}
 {additional context, if any}
 VIBAN_EOF
 
 # Auto numbering (default)
-viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type}
+viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type}
+rm -f .viban/tmp/desc.md
 
 # Manual numbering (when workflow specifies)
-viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type} --ext-id "{external_id}"
+viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type} --ext-id "{external_id}"
+rm -f .viban/tmp/desc.md
 ```
 
 Use `<<'VIBAN_EOF'` (quoted) to prevent shell interpretation.
@@ -64,49 +69,30 @@ Issue #{id} registered
   Status: backlog
 ```
 
-## Step 6: Suggest Plan Mode
-
-**Skip** unless the issue clearly needs upfront design. Most issues don't.
-
-Only suggest plan mode when:
-- The issue spans multiple subsystems or requires architectural decisions
-- The description is too vague to act on without investigation
-- P0 issues where a wrong fix could make things worse
-
-**Do NOT suggest** for: single-file fixes, straightforward bugs, feature additions with clear scope, chores, refactors with obvious targets.
+## Step 6: Done
 
-When suggesting, use AskUserQuestion:
+Report the registered issue and **stop immediately**. Do not suggest next steps, do not offer to plan, do not continue.
 
-- header: "Next step", question: "This looks complex — want to plan before working on it?"
-- options:
-  - "Plan now" — Enter plan mode to analyze and design a solution
-  - "Later" — Just register, work on it later
+> **This skill ends here. No exceptions.**
 
-**"Plan now"**: `EnterPlanMode` → after approval, save to `.viban/plans/{issue-id}.md`:
-
-```bash
-mkdir -p .viban/plans
-```
-
-```markdown
-# Plan: {issue title}
-> Issue #{id} | {priority} | {type} | Created: {timestamp}
-
-{full plan content}
-```
-
-Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-load it.`
+## Rules
 
-**"Later"**: end skill.
+### READ-ONLY MODE — This skill must NOT modify any files.
 
-> **Bias towards skipping.** When in doubt, just register and finish.
+**Allowed tools (whitelist — everything else is FORBIDDEN):**
+- `Bash`: ONLY for `mkdir -p .viban/tmp`, `viban add`, `viban list`, `cat .viban/workflow.md`, `rm -f .viban/tmp/desc.md`
+- `Write`: ONLY for `.viban/tmp/desc.md` (temp file for `--desc-file`)
+- `AskUserQuestion`: for clarification
+- `Read`: for reading `.viban/workflow.md`
 
-## Rules
+**FORBIDDEN tools and actions:**
+- `Edit`: NEVER use. No file modifications of any kind.
+- `Write` to any path outside `/tmp/viban-*.md` and `.viban/plans/`: FORBIDDEN.
+- `Bash` for anything other than `viban` CLI and `cat`/`mkdir` above: FORBIDDEN.
+- No `git` commands. No source code reads. No codebase exploration.
 
-- **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban add`, `viban list`, etc.)
-- **NEVER edit, create, or modify any source code files** — this skill registers issues only
-- **NEVER start implementation** — even after plan mode, just save the plan and stop
-- No codebase exploration — assignee does that in `/viban:assign`
+### Additional rules:
+- **NEVER read or write `viban.json` directly** — always use `viban` CLI commands
 - No solution proposals in the issue — symptoms only
 - Check duplicates first: `viban list`
 - P0 is system-down only

package/commands/assign.md

@@ -2,6 +2,8 @@
 description: "Assign first backlog issue — clarify if unclear, then finish"
 ---
 
+> Tip: Run `/clear` before `/viban:assign` for a clean context.
+
 Run `/viban:assign` to pick up the next backlog issue.
 
 Usage: `/viban:assign`

package/docs/CLAUDE.md

@@ -278,7 +278,8 @@ viban list              # Display kanban board
 viban add "Title" "Desc" P2 feat  # Create issue
 viban assign [session]  # Assign top backlog issue
 viban review [id]       # Move issue to review
-viban done <id>         # Mark issue as done
+viban done <id>         # Mark issue as done (card stays on board)
+viban done <id> --remove  # Delete card permanently
 viban get <id>          # Get issue details (JSON)
 viban help              # Show help
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-plugin-viban",
-  "version": "1.3.3",
+  "version": "1.3.5",
   "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
   "main": "bin/viban",
   "bin": {

package/skills/add/SKILL.md

@@ -41,17 +41,20 @@ Infer from description. Don't ask unless truly ambiguous.
 ## Step 4: Register
 
 ```bash
-cat > /tmp/viban-desc.md <<'VIBAN_EOF'
+mkdir -p .viban/tmp
+cat > .viban/tmp/desc.md <<'VIBAN_EOF'
 ## Symptoms
 {one-sentence symptom}
 {additional context, if any}
 VIBAN_EOF
 
 # Auto numbering (default)
-viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type}
+viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type}
+rm -f .viban/tmp/desc.md
 
 # Manual numbering (when workflow specifies)
-viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type} --ext-id "{external_id}"
+viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type} --ext-id "{external_id}"
+rm -f .viban/tmp/desc.md
 ```
 
 Use `<<'VIBAN_EOF'` (quoted) to prevent shell interpretation.
@@ -65,49 +68,30 @@ Issue #{id} registered
   Status: backlog
 ```
 
-## Step 6: Suggest Plan Mode
+## Step 6: Done
 
-**Skip** unless the issue clearly needs upfront design. Most issues don't.
+Report the registered issue and **stop immediately**. Do not suggest next steps, do not offer to plan, do not continue.
 
-Only suggest plan mode when:
-- The issue spans multiple subsystems or requires architectural decisions
-- The description is too vague to act on without investigation
-- P0 issues where a wrong fix could make things worse
+> **This skill ends here. No exceptions.**
 
-**Do NOT suggest** for: single-file fixes, straightforward bugs, feature additions with clear scope, chores, refactors with obvious targets.
-
-When suggesting, use AskUserQuestion:
-
-- header: "Next step", question: "This looks complex — want to plan before working on it?"
-- options:
-  - "Plan now" — Enter plan mode to analyze and design a solution
-  - "Later" — Just register, work on it later
-
-**"Plan now"**: `EnterPlanMode` → after approval, save to `.viban/plans/{issue-id}.md`:
-
-```bash
-mkdir -p .viban/plans
-```
-
-```markdown
-# Plan: {issue title}
-> Issue #{id} | {priority} | {type} | Created: {timestamp}
-
-{full plan content}
-```
-
-Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-load it.`
+## Rules
 
-**"Later"**: end skill.
+### READ-ONLY MODE — This skill must NOT modify any files.
 
-> **Bias towards skipping.** When in doubt, just register and finish.
+**Allowed tools (whitelist — everything else is FORBIDDEN):**
+- `Bash`: ONLY for `mkdir -p .viban/tmp`, `viban add`, `viban list`, `cat .viban/workflow.md`, `rm -f .viban/tmp/desc.md`
+- `Write`: ONLY for `.viban/tmp/desc.md` (temp file for `--desc-file`)
+- `AskUserQuestion`: for clarification
+- `Read`: for reading `.viban/workflow.md`
 
-## Rules
+**FORBIDDEN tools and actions:**
+- `Edit`: NEVER use. No file modifications of any kind.
+- `Write` to any path outside `/tmp/viban-*.md` and `.viban/plans/`: FORBIDDEN.
+- `Bash` for anything other than `viban` CLI and `cat`/`mkdir` above: FORBIDDEN.
+- No `git` commands. No source code reads. No codebase exploration.
 
-- **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban add`, `viban list`, etc.)
-- **NEVER edit, create, or modify any source code files** — this skill registers issues only
-- **NEVER start implementation** — even after plan mode, just save the plan and stop
-- No codebase exploration — assignee does that in `/viban:assign`
+### Additional rules:
+- **NEVER read or write `viban.json` directly** — always use `viban` CLI commands
 - No solution proposals in the issue — symptoms only
 - Check duplicates first: `viban list`
 - P0 is system-down only

package/skills/assign/SKILL.md

@@ -101,9 +101,7 @@ Clarification added to issue description.
 
 ## CRITICAL
 
-> - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban assign`, `viban get`, `viban list`, etc.)
-> - **FORBIDDEN: `viban done`** — this DELETES the card permanently. NEVER run it.
-> - **FORBIDDEN: `viban review`** — the issue stays in `in_progress` for the next work session.
+> - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban assign`, `viban get`, `viban list`, `viban done`, etc.)
 > - This command **assigns only**. Do NOT create branches, write code, or start implementation.
 > - If the issue is clear, just report and finish immediately.
 
@@ -113,3 +111,6 @@ Clarification added to issue description.
 |---------|-------------|
 | `viban assign [session]` | Assign issue |
 | `viban get <id>` | View issue |
+| `viban done <id>` | Mark as done (non-destructive) |
+| `viban done <id> --remove` | Delete card permanently |
+| `viban review [id]` | Move to review |

package/skills/setup/SKILL.md

@@ -211,15 +211,15 @@ Ask only what the agent **cannot infer on its own**. One AskUserQuestion call, 3
   - "Stop before commit — I'll review the code first (review in terminal/IDE)"
 - multiSelect: false
 
-**Q2. Issue Numbering**
-- header: "Issue ID"
-- question: "How should issues be numbered when using `/viban:add`?"
+**Q2. Issue Tracker Sync**
+- header: "Sync"
+- question: "Sync issues with an external tracker (GitHub Issues, Jira, Linear, etc.)?"
 - options:
-  - "Auto — viban auto-assigns #1, #2, #3..."
-  - "Sync with provider — use `/viban:sync` to import from GitHub, Jira, Linear, etc."
-  - "Manual — ask for an external ID each time (e.g. PROJ-42, JIRA-123)"
+  - "Yes — set up two-way sync (issues imported from provider)"
+  - "No — auto-number locally (#1, #2, #3...)"
+  - "No — but use manual external IDs (e.g. PROJ-42)"
 - multiSelect: false
-- If user selects "Sync with provider", run `/viban:sync` to initialize sync after workflow setup completes.
+- If user selects "Yes", run `viban sync` to initialize sync after workflow setup completes.
 
 **Q3. Extra Rules**
 
@@ -302,12 +302,12 @@ Combine **auto-detected values** (Step 7) with **interview answers** (Step 8) to
 | Value | Source | Example |
 |-------|--------|---------|
 | Pipeline | Q1 | "Full auto" or "Stop before PR" |
-| Issue numbering | Q2 | "Auto" or "Manual" |
+| Issue tracker sync | Q2 | "Yes (sync)" or "No (auto)" or "No (manual IDs)" |
 | Extra rules | Q3 | User-typed rules or "None" |
 
 **Workflow generation principles:**
 - **Q1 (Pipeline) determines the entire automation structure** — which phases run automatically, where to stop, and whether to create PRs. "Full auto" = no stops + auto PR. "Stop before PR" = auto commit + user creates PR. "Stop before commit" = implement only + user reviews.
-- **Q2 (Issue numbering) determines how `/viban:add` handles IDs.** "Auto" = viban auto-assigns `#1`, `#2`. "Sync with provider" = use `/viban:sync` to import/sync issues from GitHub, Jira, Linear, etc. "Manual" = agent asks for an external ID each time and passes `--ext-id` to `viban add`. When manual, commits/PRs reference the external ID instead of `#N`.
+- **Q2 (Issue tracker sync) determines how issues are managed.** "Yes" = run `viban sync` after setup to import/sync issues from external tracker (GitHub, Jira, Linear, etc.), IDs come from provider. "No — auto-number" = viban auto-assigns `#1`, `#2`. "No — manual IDs" = agent asks for an external ID each time and passes `--ext-id` to `viban add`. When manual, commits/PRs reference the external ID instead of `#N`.
 - **Q3 (Extra rules) is appended verbatim to the Additional Rules section.** If user mentions conventions, evidence, CHANGELOG, language, etc., incorporate into the relevant phase.
 - **Commit/PR conventions are auto-detected from git history** (Step 7.2). If the user overrides via Q3, use the user's preference instead.
 - **Everything else uses smart defaults.** Analysis depth, implementation approach, quality gates, verification methods, issue numbering, post-merge — all auto-determined by the agent or set to sensible defaults.
@@ -413,7 +413,7 @@ If build/test fails: fix errors, return to Phase 3.
 
 ## Issue Management
 
-- Issue numbering: {FROM Q2: "Auto" = auto-increment (viban default), "Sync with provider" = use `/viban:sync` for external tracker integration, "Manual" = ask for external ID via `--ext-id` flag}
+- Issue tracking: {FROM Q2: "Yes" = synced with external tracker via `viban sync`, "No — auto-number" = auto-increment (viban default), "No — manual IDs" = ask for external ID via `--ext-id` flag}
 - Test evidence: include test output in PR body
 - Post-merge: auto-close issue (`viban done {id}`), delete branch