claude-plugin-viban 1.3.2 → 1.3.4

package/.claude-plugin/plugin.json

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

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/commands/parallel-assign.md

@@ -16,8 +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.2",
+  "version": "1.3.4",
   "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/parallel-assign/SKILL.md

@@ -139,21 +139,14 @@ 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}
-   ```
-
-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.
+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.
@@ -178,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
@@ -269,9 +284,10 @@ 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
 
 ---