claude-plugin-viban 1.3.1 → 1.3.3

package/.claude-plugin/plugin.json

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

package/commands/add.md

@@ -6,6 +6,8 @@ description: "Register a problem as a viban issue"
 
 Register a problem as a viban issue. No codebase exploration, no solutions — symptoms only.
 
+> **CLI only** (no direct viban.json access)
+
 **Input**: `$ARGUMENTS`
 
 ## Step 1: Clarify (only if vague)
@@ -101,6 +103,7 @@ Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-lo
 
 ## Rules
 
+- **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`

package/commands/assign.md

@@ -12,3 +12,5 @@ What it does:
 3. That's it — no implementation, no branch creation
 
 This command is for **assignment and clarification only**. Use other tools to start working on the assigned issue.
+
+**IMPORTANT:** Never read or write `viban.json` directly — always use `viban` CLI commands.

package/commands/parallel-assign.md

@@ -16,6 +16,8 @@ Examples:
 
 How it works:
 1. Assigns N backlog issues and creates isolated git worktrees (`.viban/worktrees/{id}`)
-2. Spawns one opus agent per issue — each agent works exclusively in its own worktree
-3. Agents analyze, implement, commit, push, and create PRs independently
-4. Coordinator collects results, runs tests, and cleans up worktrees
+2. Spawns one opus agent per issue — each agent only analyzes, implements, and commits
+3. Coordinator removes worktrees, verifies local branches, pushes, and creates PRs
+4. Coordinator runs tests, moves issues to review, and reports results
+
+**IMPORTANT:** Never read or write `viban.json` directly — always use `viban` CLI commands. Direct JSON access causes race conditions.

package/package.json

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

package/skills/add/SKILL.md

@@ -7,6 +7,8 @@ description: "Register a problem as a viban issue"
 
 Register a problem as a viban issue. No codebase exploration, no solutions — symptoms only.
 
+> **CLI only** (no direct viban.json access)
+
 **Input**: `$ARGUMENTS`
 
 ## Step 1: Clarify (only if vague)
@@ -102,6 +104,7 @@ Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-lo
 
 ## Rules
 
+- **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`

package/skills/assign/SKILL.md

@@ -101,8 +101,10 @@ 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.
 > - This command **assigns only**. Do NOT create branches, write code, or start implementation.
-> - Do NOT run `viban review` — the issue stays in `in_progress` for the next work session.
 > - If the issue is clear, just report and finish immediately.
 
 ## CLI Reference

package/skills/parallel-assign/SKILL.md

@@ -139,21 +139,15 @@ You are one of {N} parallel agents working in isolated git worktrees.
    Resolves: #{ID}"
    ```
 
-4. Push and create PR:
-   ```bash
-   git push -u origin {BRANCH}
-   gh pr create --title "type: title" --body "..." --base main
-   ```
-
-5. Move issue to review:
-   ```bash
-   cd {REPO_ROOT}
-   viban review {ID}
-   ```
-
-CRITICAL:
-- Always run `viban review {ID}` before finishing, even on errors.
-- Do NOT run `viban done` — the coordinator handles post-merge cleanup.
+4. That's it. Stop after committing.
+
+ABSOLUTE RULES:
+- **Your job ends after committing.** The coordinator handles push, PR creation, and issue status.
+- **FORBIDDEN: `git push`** — the coordinator pushes from the main repo after verifying.
+- **FORBIDDEN: `gh pr create`** — the coordinator creates PRs after transplanting branches.
+- **FORBIDDEN: `viban done`** — this DELETES the card permanently.
+- **FORBIDDEN: `viban review`** — the coordinator handles issue status.
+- **FORBIDDEN: reading or writing `viban.json`** — use CLI commands only.
 - Do NOT run the full test suite — the coordinator handles that.
 - Do NOT remove the worktree — the coordinator handles cleanup.
 ```
@@ -177,44 +171,66 @@ for each (ID, BRANCH) in ISSUES:
 
 1. Wait for all background agents to complete (poll via `TaskOutput`)
 2. Collect results — note successes and failures
-3. For any issue where `viban review` was not called, run it now as safety net:
-   ```bash
-   viban review $ID
-   ```
 
 ---
 
 ## Phase 3: TRANSPLANT & CLEANUP
 
-After all agents finish, for each issue:
-
-### 3.1 Verify Local Branches
-
-The local branch already exists (created by `git worktree add -b`). After worktree removal, the branch and its commits remain in the local repo.
+After all agents finish, the coordinator handles everything from the main repo root.
 
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel)
 cd "$REPO_ROOT"
+```
+
+### 3.1 Remove Worktrees (branches survive)
 
+Worktree removal does NOT delete the branch or its commits — they remain in the local repo.
+
+```bash
+for entry in "${ISSUES[@]}"; do
+    ID="${entry%%|*}"
+    WT_DIR="$REPO_ROOT/.viban/worktrees/$ID"
+    git worktree remove "$WT_DIR" --force
+done
+```
+
+### 3.2 Verify Local Branches
+
+Confirm each branch has commits from the agent:
+
+```bash
 for entry in "${ISSUES[@]}"; do
     BRANCH="${entry##*|}"
     git log --oneline -3 "$BRANCH"
 done
 ```
 
-### 3.2 Remove Worktrees
+If a branch has no new commits (agent failed), skip it and report.
 
-PRs have been created — worktrees are no longer needed:
+### 3.3 Push Branches & Create PRs
+
+For each branch with commits, push from the main repo and create a PR:
 
 ```bash
 for entry in "${ISSUES[@]}"; do
     ID="${entry%%|*}"
-    WT_DIR="$REPO_ROOT/.viban/worktrees/$ID"
-    git worktree remove "$WT_DIR" --force
+    BRANCH="${entry##*|}"
+
+    # Push the local branch to remote
+    git push -u origin "$BRANCH"
+
+    # Create PR
+    gh pr create --head "$BRANCH" --base main \
+        --title "type: title" \
+        --body "Resolves: #${ID}"
+
+    # Move issue to review
+    viban review "$ID"
 done
 ```
 
-### 3.3 Verify PRs Exist
+### 3.4 Verify PRs Exist
 
 ```bash
 for entry in "${ISSUES[@]}"; do
@@ -268,17 +284,19 @@ Worktrees cleaned up. All PRs ready for human review.
 
 ## Error Handling
 
-- **Agent fails mid-work**: coordinator calls `viban review {ID}` as safety net
+- **Agent fails mid-work**: coordinator still attempts push + PR for any commits on the branch. If no commits, skip and call `viban review {ID}` to unblock the card.
 - **Worktree creation fails**: skip that issue, log error, continue with others
-- **PR creation fails in agent**: coordinator reports it; local branch still available for manual PR
+- **Push fails**: report it; local branch still available for manual push
+- **PR creation fails**: report it; branch is already pushed, user can create PR manually
 - **Test failures**: report which branch likely caused the failure
 
 ---
 
 ## CRITICAL RULES
 
-> 1. **NEVER exit with any issue still in `in_progress`.** For every assigned issue, ensure `viban review {ID}` has been called.
-> 2. **ALWAYS clean up worktrees** after PRs are created. Worktree dirs must not linger in `.viban/worktrees/`.
+> 1. **NEVER read or write `viban.json` directly** — always use `viban` CLI commands. Direct JSON access causes race conditions and data corruption.
+> 2. **NEVER exit with any issue still in `in_progress`.** For every assigned issue, ensure `viban review {ID}` has been called.
+> 3. **ALWAYS clean up worktrees** after PRs are created. Worktree dirs must not linger in `.viban/worktrees/`.
 
 ## CLI Reference