claude-plugin-viban 1.0.0 → 1.0.4

package/.claude-plugin/plugin.json

@@ -16,6 +16,5 @@
     "issue-tracking",
     "viban"
   ],
-  "skills": "./skills/",
   "commands": "./commands/"
 }

package/README.md

@@ -1,20 +1,49 @@
 # viban
 
-**Vi**sual Kan**ban** - Terminal-based Kanban board TUI for AI-human collaborative issue tracking.
+**Vi**sual Kan**ban** - A simple, lightweight local Kanban board for AI-human collaborative issue tracking.
 
 [![CI](https://github.com/happy-nut/claude-plugin-viban/actions/workflows/ci.yml/badge.svg)](https://github.com/happy-nut/claude-plugin-viban/actions/workflows/ci.yml)
-[![npm version](https://badge.fury.io/js/%40happy-nut%2Fclaude-plugin-viban.svg)](https://www.npmjs.com/package/@happy-nut/claude-plugin-viban)
+[![npm version](https://badge.fury.io/js/claude-plugin-viban.svg)](https://www.npmjs.com/package/claude-plugin-viban)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
+## Why viban?
+
+- **No Worktree Complexity** - Just a single JSON file. No git worktrees, no complex setup.
+- **Lightweight & Fast** - Pure shell script with minimal dependencies. Starts instantly.
+- **Local First** - Your issues stay in your repo. No external services or accounts needed.
+- **AI-Native** - Built for Claude Code integration from the ground up.
+
+## Recommended Workflow
+
+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**: QA your product, find issues, run `/task` to register them
+- **Session 2**: Run `/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.
+
 ## Features
 
 - **3-Column Kanban Board**: `backlog` → `in_progress` → `review` → `done`
 - **Priority Levels**: P0 (critical) to P3 (low priority)
-- **Type Tags**: bug, feat, chore, refactor, docs, test
+- **Type Tags**: bug, feat, chore, refactor
 - **TUI Navigation**: Interactive terminal UI with gum
 - **Parallel Sessions**: Multiple Claude Code sessions can work simultaneously
 - **Session Assignment**: Prevents duplicate work across parallel agents
-- **Claude Code Integration**: Built-in skills for automated issue resolution
+- **Claude Code Integration**: Built-in commands for automated issue resolution
 
 ## Requirements
 
@@ -24,7 +53,17 @@
 
 ## Installation
 
-### Via npm (Recommended)
+### One-liner (Recommended)
+
+Installs all dependencies (zsh, gum, jq) and viban automatically:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/happy-nut/claude-plugin-viban/main/install.sh | bash
+```
+
+### Via npm
+
+If you already have zsh, gum, and jq installed:
 
 ```bash
 npm install -g claude-plugin-viban
@@ -76,7 +115,7 @@ source ~/.zshrc
 
 ### Claude Code Plugin
 
-To use viban skills in Claude Code:
+To use viban commands in Claude Code:
 
 ```bash
 # Add as plugin marketplace
@@ -85,9 +124,12 @@ To use viban skills in Claude Code:
 # Install the plugin
 /plugin install viban
 
+# Install dependencies (first time only)
+/setup
+
 # Now you can use:
-/viban:assign
-/viban:todo
+/assign
+/task
 ```
 
 ## Usage
@@ -146,9 +188,9 @@ viban get 3
 
 ### Claude Code Integration
 
-viban provides two skills for automated issue management in Claude Code:
+viban provides commands for automated issue management in Claude Code:
 
-#### `/viban:assign` - Auto-resolve next issue
+#### `/assign` - Auto-resolve next issue
 
 Automatically picks the highest priority backlog issue and executes the full resolution workflow:
 
@@ -162,7 +204,7 @@ Automatically picks the highest priority backlog issue and executes the full res
 - Parallel agent workflows
 - Pre-prioritized backlog processing
 
-#### `/viban:todo` - Create structured issue
+#### `/task` - Create structured issue
 
 Analyzes a problem and creates a properly structured viban issue:
 
@@ -268,7 +310,7 @@ Issues are stored in `viban.json`:
 
 Multiple Claude Code sessions can work simultaneously:
 
-1. Each session calls `/viban:assign`
+1. Each session calls `/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`
@@ -287,14 +329,14 @@ claude-plugin-viban/
 │       └── release.yml      # NPM publishing
 ├── bin/
 │   └── viban                # Main TUI/CLI script
-├── commands/                # Claude Code commands (deprecated)
 ├── docs/
 │   └── CLAUDE.md            # Claude Code integration guide
 ├── scripts/
 │   └── check-deps.sh        # Dependency checker
-├── skills/
-│   ├── assign/              # /viban:assign skill
-│   └── todo/                # /viban:todo skill
+├── commands/
+│   ├── assign.md            # /assign command
+│   ├── setup.md             # /setup command
+│   └── task.md              # /task command
 ├── LICENSE                  # MIT License
 ├── package.json             # NPM package config
 └── README.md                # This file
@@ -356,6 +398,6 @@ MIT License - see [LICENSE](LICENSE) file for details.
 
 ## Links
 
-- [npm package](https://www.npmjs.com/package/@happy-nut/claude-plugin-viban)
+- [npm package](https://www.npmjs.com/package/claude-plugin-viban)
 - [Documentation](https://github.com/happy-nut/claude-plugin-viban/tree/main/docs)
 - [Issues](https://github.com/happy-nut/claude-plugin-viban/issues)

package/commands/assign.md

@@ -1,14 +1,188 @@
 ---
 name: assign
-description: "Assign and resolve first backlog issue from viban board"
+description: "Assign and resolve first backlog issue from viban board through to PR completion"
 ---
 
 # /assign
 
-Invokes the `viban:assign` skill to handle the complete workflow:
-- Assign first backlog issue
-- Analyze and resolve
-- Create PR
-- Move to review status
+Workflow: First backlog issue → Resolve → PR completion
 
-Usage: `/assign`
+> **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 |

package/commands/setup.md

@@ -0,0 +1,140 @@
+---
+name: setup
+description: "Install viban dependencies (zsh, gum, jq) automatically"
+---
+
+# /setup - Install Dependencies
+
+Automatically install all viban dependencies based on the operating system.
+
+## Execution Steps
+
+### Step 1: Detect OS and Package Manager
+
+```bash
+# Detect OS
+if [[ "$OSTYPE" == "darwin"* ]]; then
+    OS="macos"
+    PKG_MANAGER="brew"
+elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
+    OS="linux"
+    if command -v apt &> /dev/null; then
+        PKG_MANAGER="apt"
+    elif command -v dnf &> /dev/null; then
+        PKG_MANAGER="dnf"
+    elif command -v pacman &> /dev/null; then
+        PKG_MANAGER="pacman"
+    fi
+fi
+```
+
+Report detected OS and package manager to user.
+
+### Step 2: Check Existing Dependencies
+
+Check which dependencies are already installed:
+
+```bash
+command -v zsh &> /dev/null && echo "✓ zsh" || echo "✗ zsh"
+command -v gum &> /dev/null && echo "✓ gum" || echo "✗ gum"
+command -v jq &> /dev/null && echo "✓ jq" || echo "✗ jq"
+command -v viban &> /dev/null && echo "✓ viban" || echo "✗ viban"
+```
+
+### Step 3: Install Missing Dependencies
+
+For each missing dependency, run the appropriate install command:
+
+#### macOS (Homebrew)
+
+```bash
+# Install Homebrew if not present
+if ! command -v brew &> /dev/null; then
+    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+fi
+
+# Install dependencies
+brew install zsh gum jq
+```
+
+#### Linux (apt - Debian/Ubuntu)
+
+```bash
+# Install zsh and jq
+sudo apt update
+sudo apt install -y zsh jq
+
+# Install gum (requires Charm repo)
+sudo mkdir -p /etc/apt/keyrings
+curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg
+echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list
+sudo apt update
+sudo apt install -y gum
+```
+
+#### Linux (dnf - Fedora/RHEL)
+
+```bash
+sudo dnf install -y zsh jq
+
+# Install gum
+echo '[charm]
+name=Charm
+baseurl=https://repo.charm.sh/yum/
+enabled=1
+gpgcheck=1
+gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo
+sudo dnf install -y gum
+```
+
+#### Linux (pacman - Arch)
+
+```bash
+sudo pacman -S --noconfirm zsh jq gum
+```
+
+### Step 4: Install viban CLI
+
+```bash
+npm install -g claude-plugin-viban
+```
+
+### Step 5: Verify Installation
+
+```bash
+viban help
+```
+
+If successful, show:
+
+```
+╭─────────────────────────────────────╮
+│      viban setup complete! 🎉       │
+╰─────────────────────────────────────╯
+
+All dependencies installed:
+  ✓ zsh
+  ✓ gum
+  ✓ jq
+  ✓ viban
+
+You can now use:
+  viban              Open TUI board
+  viban add "task"   Add a task
+  viban list         List all tasks
+  /assign            Auto-resolve next issue
+  /task              Create structured issue
+```
+
+## Error Handling
+
+- **Homebrew not found on macOS**: Prompt user to install Homebrew first
+- **sudo required on Linux**: Inform user that admin privileges are needed
+- **Package manager not found**: Show manual installation instructions
+- **npm not found**: Install Node.js first
+
+## Notes
+
+- This command requires terminal access to run shell commands
+- On Linux, sudo password may be required
+- All commands are idempotent (safe to run multiple times)

package/{skills/todo/SKILL.md → commands/task.md}

@@ -1,13 +1,9 @@
 ---
-name: viban:todo
-description: "Analyze problem situation and register as viban issue (focus on symptoms and problem definition)"
-category: development
-complexity: medium
-mcp-servers: []
-personas: []
+name: task
+description: "Analyze problem and register as viban issue with evidence"
 ---
 
-# /viban:todo - Problem Analysis and Issue Registration
+# /task - Problem Analysis and Issue Registration
 
 Analyze problem situation and register as viban issue with file locations and evidence.
 

package/install.sh

@@ -0,0 +1,219 @@
+#!/bin/bash
+# viban - One-liner installer
+# Usage: curl -fsSL https://raw.githubusercontent.com/happy-nut/claude-plugin-viban/main/install.sh | bash
+
+set -e
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[0;33m'
+BLUE='\033[0;34m'
+BOLD='\033[1m'
+NC='\033[0m'
+
+echo ""
+echo -e "${BOLD}${BLUE}╭─────────────────────────────────────╮${NC}"
+echo -e "${BOLD}${BLUE}│         viban installer             │${NC}"
+echo -e "${BOLD}${BLUE}╰─────────────────────────────────────╯${NC}"
+echo ""
+
+# Detect OS
+OS="unknown"
+PKG_MANAGER=""
+
+if [[ "$OSTYPE" == "darwin"* ]]; then
+    OS="macos"
+    if command -v brew &> /dev/null; then
+        PKG_MANAGER="brew"
+    else
+        echo -e "${RED}Error: Homebrew is required on macOS${NC}"
+        echo -e "Install it first: ${YELLOW}/bin/bash -c \"\$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)\"${NC}"
+        exit 1
+    fi
+elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
+    OS="linux"
+    if command -v apt &> /dev/null; then
+        PKG_MANAGER="apt"
+    elif command -v dnf &> /dev/null; then
+        PKG_MANAGER="dnf"
+    elif command -v pacman &> /dev/null; then
+        PKG_MANAGER="pacman"
+    else
+        echo -e "${RED}Error: No supported package manager found (apt, dnf, pacman)${NC}"
+        exit 1
+    fi
+else
+    echo -e "${RED}Error: Unsupported OS: $OSTYPE${NC}"
+    exit 1
+fi
+
+echo -e "${GREEN}✓${NC} Detected: $OS ($PKG_MANAGER)"
+
+# Install system dependencies
+install_pkg() {
+    local name="$1"
+
+    if command -v "$name" &> /dev/null; then
+        echo -e "${GREEN}✓${NC} $name already installed"
+        return 0
+    fi
+
+    echo -e "${YELLOW}→${NC} Installing $name..."
+
+    case "$PKG_MANAGER" in
+        brew)
+            brew install "$name"
+            ;;
+        apt)
+            sudo apt update -qq
+            sudo apt install -y "$name"
+            ;;
+        dnf)
+            sudo dnf install -y "$name"
+            ;;
+        pacman)
+            sudo pacman -S --noconfirm "$name"
+            ;;
+    esac
+
+    echo -e "${GREEN}✓${NC} $name installed"
+}
+
+# Install gum (special case for Linux - needs Charm repo)
+install_gum() {
+    if command -v gum &> /dev/null; then
+        echo -e "${GREEN}✓${NC} gum already installed"
+        return 0
+    fi
+
+    echo -e "${YELLOW}→${NC} Installing gum..."
+
+    case "$PKG_MANAGER" in
+        brew)
+            brew install gum
+            ;;
+        apt)
+            # Add Charm repository
+            sudo mkdir -p /etc/apt/keyrings
+            curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg 2>/dev/null || true
+            echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list > /dev/null
+            sudo apt update -qq
+            sudo apt install -y gum
+            ;;
+        dnf)
+            echo '[charm]
+name=Charm
+baseurl=https://repo.charm.sh/yum/
+enabled=1
+gpgcheck=1
+gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo > /dev/null
+            sudo dnf install -y gum
+            ;;
+        pacman)
+            sudo pacman -S --noconfirm gum
+            ;;
+    esac
+
+    echo -e "${GREEN}✓${NC} gum installed"
+}
+
+echo ""
+echo -e "${BOLD}Installing dependencies...${NC}"
+echo ""
+
+# Install zsh (required for viban script)
+install_pkg "zsh"
+
+# Install jq
+install_pkg "jq"
+
+# Install gum
+install_gum
+
+# Check for npm
+echo ""
+if ! command -v npm &> /dev/null; then
+    echo -e "${YELLOW}→${NC} Installing Node.js..."
+    case "$PKG_MANAGER" in
+        brew)
+            brew install node
+            ;;
+        apt)
+            curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
+            sudo apt install -y nodejs
+            ;;
+        dnf)
+            sudo dnf install -y nodejs
+            ;;
+        pacman)
+            sudo pacman -S --noconfirm nodejs npm
+            ;;
+    esac
+    echo -e "${GREEN}✓${NC} Node.js installed"
+else
+    echo -e "${GREEN}✓${NC} npm already installed"
+fi
+
+# Install viban via npm
+echo ""
+echo -e "${BOLD}Installing viban...${NC}"
+echo ""
+
+npm install -g claude-plugin-viban
+
+echo ""
+echo -e "${GREEN}✓${NC} viban installed globally"
+
+# Register Claude Code plugin
+echo ""
+echo -e "${BOLD}Registering Claude Code plugin...${NC}"
+echo ""
+
+CLAUDE_CONFIG_DIR="${HOME}/.claude"
+CLAUDE_PLUGINS_FILE="${CLAUDE_CONFIG_DIR}/plugins.json"
+
+mkdir -p "$CLAUDE_CONFIG_DIR"
+
+# Get npm global prefix to find viban
+NPM_PREFIX=$(npm prefix -g)
+VIBAN_PLUGIN_DIR="${NPM_PREFIX}/lib/node_modules/claude-plugin-viban"
+
+# Check if plugins.json exists
+if [[ -f "$CLAUDE_PLUGINS_FILE" ]]; then
+    # Check if viban is already registered
+    if jq -e '.plugins[] | select(.name == "viban")' "$CLAUDE_PLUGINS_FILE" > /dev/null 2>&1; then
+        echo -e "${GREEN}✓${NC} Plugin already registered"
+    else
+        # Add viban to existing plugins
+        jq --arg path "$VIBAN_PLUGIN_DIR" '.plugins += [{"name": "viban", "path": $path}]' "$CLAUDE_PLUGINS_FILE" > "${CLAUDE_PLUGINS_FILE}.tmp"
+        mv "${CLAUDE_PLUGINS_FILE}.tmp" "$CLAUDE_PLUGINS_FILE"
+        echo -e "${GREEN}✓${NC} Plugin registered"
+    fi
+else
+    # Create new plugins.json
+    cat > "$CLAUDE_PLUGINS_FILE" << EOF
+{
+  "plugins": [
+    {
+      "name": "viban",
+      "path": "$VIBAN_PLUGIN_DIR"
+    }
+  ]
+}
+EOF
+    echo -e "${GREEN}✓${NC} Plugin registered"
+fi
+
+echo ""
+echo -e "${BOLD}${GREEN}╭─────────────────────────────────────╮${NC}"
+echo -e "${BOLD}${GREEN}│      Installation complete! 🎉      │${NC}"
+echo -e "${BOLD}${GREEN}╰─────────────────────────────────────╯${NC}"
+echo ""
+echo -e "Usage:"
+echo -e "  ${YELLOW}viban${NC}              Open TUI board"
+echo -e "  ${YELLOW}viban add \"task\"${NC}   Add a task"
+echo -e "  ${YELLOW}viban list${NC}         List all tasks"
+echo -e "  ${YELLOW}viban help${NC}         Show all commands"
+echo ""
+echo -e "In Claude Code, the plugin is now available."
+echo ""

package/package.json

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

package/commands/todo.md

@@ -1,15 +0,0 @@
----
-name: todo
-description: "Analyze problem and register as viban issue"
----
-
-# /todo
-
-Invokes the `viban:todo` skill to:
-- Analyze problem situation
-- Search codebase for evidence
-- Register issue with proper priority and type
-
-Usage:
-- `/todo` (will prompt for details)
-- `/todo "Charts not showing on results page"`

package/skills/assign/SKILL.md

@@ -1,203 +0,0 @@
----
-name: viban:assign
-description: "Assign and resolve the first backlog issue from viban board through to PR completion. Reads project CLAUDE.md for workflow."
-category: debugging
-complexity: advanced
-mcp-servers: [serena]
-personas: []
----
-
-# /viban: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 "⚠️ 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
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
----
-
-## Phase 4: REFLECT (if available)
-
-> **Optional**: Run `/self-reflect` if project has this skill
-
-```
-/self-reflect
-```
-
----
-
-## 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
-[ ] Self-reflection done (if available)
-```
-
----
-
-## 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 |