claude-plugin-viban 1.3.1 → 1.3.2

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "viban",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "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

@@ -19,3 +19,5 @@ How it works:
 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
+
+**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.2",
   "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

@@ -151,9 +151,10 @@ You are one of {N} parallel agents working in isolated git worktrees.
    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.
+ABSOLUTE RULES (violating any of these corrupts the board):
+- Run `viban review {ID}` as your LAST command before finishing. Always. Even on errors.
+- **FORBIDDEN: `viban done`** — this DELETES the card permanently. NEVER run it. Only the human runs `viban done` after reviewing the PR.
+- **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.
 ```
@@ -277,8 +278,9 @@ Worktrees cleaned up. All PRs ready for human review.
 
 ## 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