claude-plugin-viban 1.0.4 → 1.0.14

package/.claude-plugin/marketplace.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "viban-marketplace",
+  "version": "1.0.0",
+  "description": "viban plugin marketplace",
+  "owner": {
+    "name": "happy-nut",
+    "email": "happy-nut@users.noreply.github.com"
+  },
+  "plugins": [
+    {
+      "name": "viban",
+      "description": "Simple, lightweight local Kanban board for AI-human collaborative issue tracking",
+      "version": "1.0.14",
+      "author": {
+        "name": "happy-nut"
+      },
+      "source": "./",
+      "category": "productivity"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "viban",
-  "version": "1.0.0",
+  "version": "1.0.14",
   "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
   "author": {
     "name": "happy-nut"
@@ -16,5 +16,5 @@
     "issue-tracking",
     "viban"
   ],
-  "commands": "./commands/"
+  "skills": "./skills/"
 }

package/README.md

@@ -18,19 +18,19 @@
 The most effective way to use viban is with **multiple terminal sessions**:
 
 ```
-┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐
-│   Session 1     │  │   Session 2     │  │   Session 3     │
-│                 │  │                 │  │                 │
-│  Product QA     │  │  Issue Work     │  │  viban TUI      │
-│  + /task        │  │  + /assign      │  │                 │
-│                 │  │                 │  │  (always open)  │
-│  Find bugs,     │  │  Pick & resolve │  │  Monitor board  │
-│  register issues│  │  issues         │  │  in real-time   │
-└─────────────────┘  └─────────────────┘  └─────────────────┘
+┌───────────────────┐  ┌───────────────────┐  ┌───────────────────┐
+│    Session 1      │  │    Session 2      │  │    Session 3      │
+│                   │  │                   │  │                   │
+│  Product QA       │  │  Issue Work       │  │  viban TUI        │
+│  + /viban:task    │  │  + /viban:assign  │  │                   │
+│                   │  │                   │  │  (always open)    │
+│  Find bugs,       │  │  Pick & resolve   │  │  Monitor board    │
+│  register issues  │  │  issues           │  │  in real-time     │
+└───────────────────┘  └───────────────────┘  └───────────────────┘
 ```
 
-- **Session 1**: QA your product, find issues, run `/task` to register them
-- **Session 2**: Run `/assign` to pick the next issue and resolve it
+- **Session 1**: QA your product, find issues, run `/viban:task` to register them
+- **Session 2**: Run `/viban:assign` to pick the next issue and resolve it
 - **Session 3**: Keep `viban` TUI open to monitor the board
 
 This separation keeps your workflow clean and prevents context switching.
@@ -125,11 +125,11 @@ To use viban commands in Claude Code:
 /plugin install viban
 
 # Install dependencies (first time only)
-/setup
+/viban:setup
 
 # Now you can use:
-/assign
-/task
+/viban:assign
+/viban:task
 ```
 
 ## Usage
@@ -190,7 +190,7 @@ viban get 3
 
 viban provides commands for automated issue management in Claude Code:
 
-#### `/assign` - Auto-resolve next issue
+#### `/viban:assign` - Auto-resolve next issue
 
 Automatically picks the highest priority backlog issue and executes the full resolution workflow:
 
@@ -204,7 +204,7 @@ Automatically picks the highest priority backlog issue and executes the full res
 - Parallel agent workflows
 - Pre-prioritized backlog processing
 
-#### `/task` - Create structured issue
+#### `/viban:task` - Create structured issue
 
 Analyzes a problem and creates a properly structured viban issue:
 
@@ -310,7 +310,7 @@ Issues are stored in `viban.json`:
 
 Multiple Claude Code sessions can work simultaneously:
 
-1. Each session calls `/assign`
+1. Each session calls `/viban:assign`
 2. Session ID is recorded in `assigned_to` field
 3. Other sessions skip already-assigned issues
 4. Completion moves issue to `review` or `done`
@@ -333,10 +333,10 @@ claude-plugin-viban/
 │   └── CLAUDE.md            # Claude Code integration guide
 ├── scripts/
 │   └── check-deps.sh        # Dependency checker
-├── commands/
-│   ├── assign.md            # /assign command
-│   ├── setup.md             # /setup command
-│   └── task.md              # /task command
+├── skills/
+│   ├── assign/SKILL.md      # /viban:assign skill
+│   ├── setup/SKILL.md       # /viban:setup skill
+│   └── task/SKILL.md        # /viban:task skill
 ├── LICENSE                  # MIT License
 ├── package.json             # NPM package config
 └── README.md                # This file

package/bin/viban

@@ -33,10 +33,11 @@ check_dependencies() {
 # Only check dependencies for interactive commands (not help)
 [[ "$1" != "help" && "$1" != "--help" && "$1" != "-h" ]] && check_dependencies
 
+IN_TUI=false
 cleanup() {
     printf '\033[?25h\033[0m'
     stty echo 2>/dev/null
-    clear
+    $IN_TUI && clear
     exit 0
 }
 trap cleanup INT TERM EXIT
@@ -147,8 +148,8 @@ CACHED_COL_W=32
 CACHED_MAX_H=22
 CACHED_MAX_TASKS=7
 
-# Spinner for in_progress cards (ASCII to avoid width calculation issues)
-SPINNER_FRAMES=('|' '/' '-' '\')
+# Spinner for in_progress cards (Braille dots - consistent 1-char width)
+SPINNER_FRAMES=('⠋' '⠙' '⠹' '⠸' '⠼' '⠴' '⠦' '⠧' '⠇' '⠏')
 SPINNER_IDX=0
 
 update_term_cache() {
@@ -744,6 +745,7 @@ delete_issue() {
 }
 
 level1_columns() {
+    IN_TUI=true
     local col=0 card=0
 
     # Hide cursor and disable input echo

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-plugin-viban",
-  "version": "1.0.4",
+  "version": "1.0.14",
   "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
   "main": "bin/viban",
   "bin": {
@@ -9,7 +9,7 @@
   "files": [
     "bin/",
     "scripts/",
-    "commands/",
+    "skills/",
     "docs/",
     ".claude-plugin/",
     "install.sh",

package/skills/assign/SKILL.md

@@ -0,0 +1,216 @@
+---
+name: assign
+description: "Assign and resolve first backlog issue from viban board through to PR completion"
+---
+
+# /assign
+
+Workflow: First backlog issue -> Resolve -> PR completion
+
+> **No direct `viban.json` access** - CLI only
+> **No Worktree** - Work directly on branch in main repo
+> **Workflow**: Read CLAUDE.md first, follow project workflow if exists
+
+---
+
+## Phase 0: CONTEXT & SETUP
+
+### 0.1 Read Project Workflow (CRITICAL)
+
+Before any work, read the project's CLAUDE.md:
+
+```bash
+for path in "./CLAUDE.md" "./.claude/CLAUDE.md" "../CLAUDE.md"; do
+    [ -f "$path" ] && cat "$path"
+done
+```
+
+Look for:
+- `Issue Resolution Workflow` or `Workflow` section
+- Testing requirements (manual verification, specific tools, etc.)
+
+IMPORTANT:
+- If project has a defined workflow -> MUST follow it exactly
+- If no workflow found -> Use default workflow (Phase 1 below)
+
+### 0.2 Git Setup
+
+```bash
+# 1. Check for uncommitted changes
+if [ -n "$(git status --porcelain)" ]; then
+    echo "Warning: Uncommitted changes detected"
+    # Ask user whether to commit (use AskUserQuestion)
+fi
+
+# 2. Switch to main branch and sync
+git checkout main
+git fetch origin main
+git reset --hard origin/main
+
+# 3. Assign issue
+ISSUE_ID=$(viban assign 2>&1 | tail -1)
+if [ -z "$ISSUE_ID" ] || [ "$ISSUE_ID" = "No backlog" ]; then
+    echo "No issues in backlog"
+    exit 0
+fi
+
+# 4. Create new branch
+git checkout -b viban-$ISSUE_ID
+```
+
+If backlog is empty: Notify user and exit
+
+---
+
+## Phase 1: ANALYZE & IMPLEMENT
+
+```bash
+viban get $ISSUE_ID
+```
+
+### If Project Workflow Exists (from CLAUDE.md):
+
+Follow the project's exact steps.
+
+### Default Workflow (if no project workflow):
+
+1. **Understand**: Read the issue, understand the problem
+2. **Locate**: Find relevant code files
+3. **Analyze**: Determine root cause
+4. **Implement**: Make minimal, focused changes
+
+---
+
+## Phase 2: VERIFY
+
+Manual verification using available tools. Do NOT run build/test here - save that for Phase 3.
+
+### Verification Methods (use what's appropriate):
+
+| Type | Tool | Usage |
+|------|------|-------|
+| Web UI | Playwright MCP | `browser_navigate`, `browser_snapshot`, `browser_click` |
+| API | WebFetch | Fetch endpoints, check responses |
+| CLI | Bash | Run the CLI command, check output |
+| Visual | Read | Read screenshot files if provided |
+| Browser | Chrome DevTools MCP | `take_snapshot`, `navigate_page`, `click` |
+
+### Verification Steps:
+
+1. **Identify verification target**: What proves this fix works?
+2. **Execute verification**: Use appropriate tool from above
+3. **Confirm result**: Does the actual behavior match expected?
+4. **Document evidence**: Note what was verified and how
+
+Example verifications:
+- Web feature: Navigate to page, take snapshot, verify element exists
+- API fix: Fetch endpoint, check response status and body
+- CLI change: Run command, verify output format
+- UI bug: Navigate, interact, confirm no error
+
+If verification fails: Return to Phase 1, fix the issue, re-verify.
+
+---
+
+## Phase 3: SHIP
+
+### 3.1 Run Build & Tests
+
+```bash
+# Run project's build/test commands
+# Example: npm run build && npm test
+# Example: pytest
+# Example: cargo build && cargo test
+```
+
+If build/test fails: Fix errors, return to Phase 2 for re-verification.
+
+### 3.2 Rebase
+
+```bash
+git fetch origin main
+git rebase origin/main
+# On conflict: resolve -> git add -> git rebase --continue
+```
+
+### 3.3 Commit & Push
+
+```bash
+git add -A
+git commit -m "fix: issue title summary
+
+- Root cause: ...
+- Solution: ...
+
+Resolves: viban-$ISSUE_ID"
+
+git push -u origin viban-$ISSUE_ID
+```
+
+### 3.4 Create PR
+
+```bash
+EXISTING_PR=$(gh pr list --head viban-$ISSUE_ID --json number -q '.[0].number')
+[ -z "$EXISTING_PR" ] && gh pr create \
+    --title "viban-$ISSUE_ID: title" \
+    --body "## Changes
+- ...
+
+## Verification
+- [ ] Manual verification completed
+- [ ] Build passing
+- [ ] Tests passing (if applicable)" \
+    --base main
+```
+
+### 3.5 Issue -> review
+
+```bash
+viban review $ISSUE_ID
+```
+
+---
+
+## Phase 4: HANDOFF
+
+```
+Human Review Required
+
+Issue #$ISSUE_ID -> review status
+
+PR: gh pr view viban-$ISSUE_ID --web
+
+Verification complete:
+   - Manual verification done with available tools
+   - Build passing
+   - Project workflow followed
+
+After approval: Delete issue from viban TUI
+```
+
+---
+
+## Checklist
+
+```
+[ ] Read CLAUDE.md for project workflow
+[ ] Working on viban-$ISSUE_ID branch
+[ ] Implementation complete
+[ ] Manual verification passed (using appropriate tools)
+[ ] Build & tests passing
+[ ] Rebase complete
+[ ] PR created
+[ ] viban review executed
+```
+
+---
+
+## CLI Reference
+
+| Command | Description |
+|---------|-------------|
+| `viban` | Open TUI |
+| `viban list` | Print board |
+| `viban assign [session]` | Assign issue |
+| `viban get <id>` | View issue |
+| `viban review <id>` | Move to review |

package/commands/assign.md

@@ -1,188 +0,0 @@
----
-name: assign
-description: "Assign and resolve first backlog issue from viban board through to PR completion"
----
-
-# /assign
-
-Workflow: First backlog issue → Resolve → PR completion
-
-> **No direct `viban.json` access** — CLI only
-> **No Worktree** — Work directly on branch in main repo
-> **Workflow**: Read CLAUDE.md first, follow project workflow if exists
-
----
-
-## Phase 0: CONTEXT & SETUP
-
-### 0.1 Read Project Workflow (CRITICAL)
-
-**Before any work, read the project's CLAUDE.md:**
-
-```bash
-# Check for CLAUDE.md at common locations
-for path in "./CLAUDE.md" "./.claude/CLAUDE.md" "../CLAUDE.md"; do
-    [ -f "$path" ] && cat "$path"
-done
-```
-
-**Look for:**
-- `Issue Resolution Workflow` section
-- `Workflow` or `Development Process` section
-- Specific steps like `ultrawork`, `code-simplifier`, `code-review`
-- Testing requirements (`pytest`, manual verification, etc.)
-
-**IMPORTANT:**
-- If project has a defined workflow → **MUST follow it exactly**
-- If no workflow found → Use default workflow (Phase 1 below)
-
-### 0.2 Git Setup
-
-```bash
-# 1. Check for uncommitted changes
-if [ -n "$(git status --porcelain)" ]; then
-    echo "Warning: Uncommitted changes detected"
-    # → Ask user whether to commit (use AskUserQuestion)
-fi
-
-# 2. Switch to main branch and sync
-git checkout main
-git fetch origin main
-git reset --hard origin/main
-
-# 3. Assign issue (state change only, no worktree)
-ISSUE_ID=$(viban assign 2>&1 | tail -1)
-if [ -z "$ISSUE_ID" ] || [ "$ISSUE_ID" = "No backlog" ]; then
-    echo "No issues in backlog"
-    exit 0
-fi
-
-# 4. Create new branch
-git checkout -b viban-$ISSUE_ID
-```
-
-**If backlog is empty**: Notify user and exit
-
----
-
-## Phase 1: ANALYZE → VERIFY
-
-```bash
-viban get $ISSUE_ID
-```
-
-### If Project Workflow Exists (from CLAUDE.md):
-
-**Follow the project's exact steps.** Common patterns include:
-
-1. Root cause analysis (5 Whys)
-2. Context verification (ask if unclear)
-3. Implementation & verification strategy
-4. Code implementation (`/ultrawork` for 2+ files)
-5. **Manual verification** (browser/API, NOT pytest)
-6. Code simplification (`/code-simplifier`)
-7. Code review (`/code-review`)
-
-### Default Workflow (if no project workflow):
-
-1. **Understand**: Read the issue, understand the problem
-2. **Locate**: Find relevant code files
-3. **Analyze**: Determine root cause
-4. **Implement**: Make minimal, focused changes
-5. **Verify**: Test the fix works (appropriate method for the project)
-6. **Review**: Self-review changes for quality
-
----
-
-## Phase 2: SHIP
-
-### 2.1 Rebase
-
-```bash
-git fetch origin main
-git rebase origin/main
-# On conflict: resolve → git add → git rebase --continue
-```
-
-### 2.2 Commit & Push
-
-```bash
-git add -A
-git commit -m "fix: issue title summary
-
-- Root cause: ...
-- Solution: ...
-
-Resolves: viban-$ISSUE_ID"
-
-git push -u origin viban-$ISSUE_ID
-```
-
-### 2.3 Create PR
-
-```bash
-EXISTING_PR=$(gh pr list --head viban-$ISSUE_ID --json number -q '.[0].number')
-[ -z "$EXISTING_PR" ] && gh pr create \
-    --title "viban-$ISSUE_ID: title" \
-    --body "## Changes
-- ...
-
-## Testing
-- [ ] Tests passing (if applicable)
-- [ ] Manual verification (if applicable)" \
-    --base main
-```
-
-### 2.4 Issue → review
-
-```bash
-viban review $ISSUE_ID
-```
-
----
-
-## Phase 3: HANDOFF
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Human Review Required
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Issue #$ISSUE_ID → review status
-
-PR: gh pr view viban-$ISSUE_ID --web
-
-Verification complete:
-   - Project workflow followed
-   - Changes tested appropriately
-   - Code reviewed
-
-After approval: Delete issue from viban TUI
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
----
-
-## Checklist
-
-```
-[ ] Read CLAUDE.md for project workflow
-[ ] Working on viban-$ISSUE_ID branch
-[ ] Project workflow steps completed (or default if none)
-[ ] Rebase complete
-[ ] PR pushed
-[ ] viban review executed
-```
-
----
-
-## CLI Reference
-
-| Command | Description |
-|---------|-------------|
-| `viban` | Open TUI |
-| `viban list` | Print board |
-| `viban assign [session]` | Assign issue |
-| `viban get <id>` | View issue |
-| `viban review <id>` | Move to review |