claude-plugin-viban 1.1.2 → 1.2.1

package/commands/assign.md

@@ -4,71 +4,64 @@ description: "Assign and resolve first backlog issue from viban board through to
 
 # /assign
 
-Workflow: First backlog issue -> Resolve -> PR completion
+First backlog issue → Resolve → PR completion
 
-> **No direct `viban.json` access** - CLI only
-> **No Worktree** - Work directly on branch in main repo
-> **Workflow**: Read `.viban/workflow.md` first, then CLAUDE.md fallback
+> **CLI only** (no direct viban.json access) | **No worktree** (branch in main repo)
 
 ---
 
-## Phase 0: CONTEXT & SETUP
+## Phase 0: SETUP
 
-### 0.1 Read Project Workflow (CRITICAL)
+### 0.1 Read Workflow (CRITICAL)
 
-Before any work, read the project's workflow configuration. Check in priority order:
-
-**Priority 1: `.viban/workflow.md`** (dedicated workflow file)
-
-```bash
-[ -f ".viban/workflow.md" ] && cat ".viban/workflow.md"
-```
-
-**Priority 2: CLAUDE.md** (legacy fallback)
-
-Only if `.viban/workflow.md` does NOT exist:
+Check in priority order — first match wins, follow it exactly:
 
+1. `.viban/workflow.md` → `[ -f ".viban/workflow.md" ] && cat ".viban/workflow.md"`
+2. CLAUDE.md (legacy, only if no workflow.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.
+3. Default workflow (Phase 1 below)
 
-Look for: `Issue Resolution Workflow` or `Workflow` section.
+### 0.2 Git Setup & Assign
 
-**Priority 3: Default workflow** (Phase 1 below)
+```bash
+# Check uncommitted changes → AskUserQuestion if dirty
+[ -n "$(git status --porcelain)" ] && echo "Warning: Uncommitted changes"
 
-IMPORTANT:
-- If `.viban/workflow.md` exists -> MUST follow it exactly (all phases)
-- Else if CLAUDE.md has a workflow section -> MUST follow it exactly
-- If no workflow found -> Use default workflow (Phase 1 below)
+git checkout main && git fetch origin main && git reset --hard origin/main
 
-### 0.2 Git Setup
+ISSUE_ID=$(viban assign 2>&1 | tail -1)
+[[ -z "$ISSUE_ID" || "$ISSUE_ID" == "No backlog" ]] && echo "No issues in backlog" && exit 0
+```
+
+### 0.3 Detect Sync & Create Branch
 
 ```bash
-# 1. Check for uncommitted changes
-if [ -n "$(git status --porcelain)" ]; then
-    echo "Warning: Uncommitted changes detected"
-    # Ask user whether to commit (use AskUserQuestion)
+ISSUE_JSON=$(viban get $ISSUE_ID)
+EXT_ID=$(echo "$ISSUE_JSON" | jq -r '.external_id // ""')
+SYNC_ACTIVE=false; EXTERNAL_NUM=""
+
+if [ -n "$EXT_ID" ] && [ "$EXT_ID" != "null" ]; then
+    SYNC_ACTIVE=true
+    EXTERNAL_NUM="${EXT_ID##*:}"  # "github:42" -> "42"
+    TITLE=$(echo "$ISSUE_JSON" | jq -r '.title' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | head -c 40)
+    git checkout -b "issue-${EXTERNAL_NUM}-${TITLE}"
+else
+    git checkout -b issue-$ISSUE_ID
 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
+### 0.4 Load Plan (if available)
 
-# 4. Create new branch
-git checkout -b viban-$ISSUE_ID
+```bash
+[ -f ".viban/plans/${ISSUE_ID}.md" ] && cat ".viban/plans/${ISSUE_ID}.md"
 ```
 
-If backlog is empty: Notify user and exit
+If plan exists: use as primary guide for Phase 1, skip redundant analysis, but verify plan is still current.
 
 ---
 
@@ -78,102 +71,105 @@ If backlog is empty: Notify user and exit
 viban get $ISSUE_ID
 ```
 
-### If Project Workflow Exists (from `.viban/workflow.md` or 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
+**With project workflow**: follow its exact steps.
+**Default** (no workflow): Understand → Locate → Analyze root cause → Implement minimal 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):
+Manual verification — do NOT run build/test here (Phase 3).
 
-| 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` |
+| Type | Tool |
+|------|------|
+| Web UI | Playwright MCP (`browser_navigate`, `browser_snapshot`, `browser_click`) |
+| API | WebFetch |
+| CLI | Bash |
+| Visual | Read (screenshot files) |
+| Browser | Chrome DevTools MCP |
 
-### Verification Steps:
+Steps: identify what proves the fix → execute → confirm behavior → document evidence.
 
-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
+Examples:
+- 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
 
-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.
+If verification fails: return to Phase 1.
 
 ---
 
 ## Phase 3: SHIP
 
-### 3.1 Run Build & Tests
+### 3.1 Build & Test
 
-```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.
+Run project's build/test commands. If fail: fix → return to Phase 2.
 
 ### 3.2 Rebase
 
 ```bash
-git fetch origin main
-git rebase origin/main
+git fetch origin main && git rebase origin/main
 # On conflict: resolve -> git add -> git rebase --continue
 ```
 
 ### 3.3 Commit & Push
 
 ```bash
+BRANCH=$(git branch --show-current)
 git add -A
-git commit -m "fix: issue title summary
+
+# Sync mode: "Closes #NUM" | Default: "Resolves: viban-ID"
+if [ "$SYNC_ACTIVE" = true ]; then
+    git commit -m "fix: issue title summary
+
+- Root cause: ...
+- Solution: ...
+
+Closes #$EXTERNAL_NUM"
+else
+    git commit -m "fix: issue title summary
 
 - Root cause: ...
 - Solution: ...
 
-Resolves: viban-$ISSUE_ID"
+Resolves: #$ISSUE_ID"
+fi
 
-git push -u origin viban-$ISSUE_ID
+git push -u origin "$BRANCH"
 ```
 
 ### 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
+EXISTING_PR=$(gh pr list --head "$BRANCH" --json number -q '.[0].number')
+
+if [ -z "$EXISTING_PR" ]; then
+    if [ "$SYNC_ACTIVE" = true ]; then
+        gh pr create --title "fix: title" \
+            --body "## Changes
+- ...
+
+Closes #$EXTERNAL_NUM
+
+## Verification
+- [ ] Manual verification completed
+- [ ] Build passing
+- [ ] Tests passing (if applicable)" --base main
+    else
+        gh pr create --title "fix: title" \
+            --body "## Changes
 - ...
 
 ## Verification
 - [ ] Manual verification completed
 - [ ] Build passing
-- [ ] Tests passing (if applicable)" \
-    --base main
+- [ ] Tests passing (if applicable)" --base main
+    fi
+fi
 ```
 
-### 3.5 Issue -> review
+### 3.5 Move to Review
 
 ```bash
 viban review $ISSUE_ID
@@ -184,18 +180,9 @@ 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
+Issue #$ISSUE_ID → review | PR: gh pr view --web
+Verification: manual + build + workflow followed
+After approval: delete issue from viban TUI
 ```
 
 ---
@@ -204,7 +191,7 @@ After approval: Delete issue from viban TUI
 
 ```
 [ ] Read .viban/workflow.md (or CLAUDE.md fallback) for project workflow
-[ ] Working on viban-$ISSUE_ID branch
+[ ] Working on issue-$ISSUE_ID branch
 [ ] Implementation complete
 [ ] Manual verification passed (using appropriate tools)
 [ ] Build & tests passing
@@ -217,13 +204,7 @@ After approval: Delete issue from viban TUI
 
 ## CRITICAL: Status Transition Rule
 
-> **NEVER end this command with the issue still in `in_progress`.**
->
-> Before exiting — whether you completed all phases or stopped early due to errors:
-> ```bash
-> viban review $ISSUE_ID
-> ```
-> This is MANDATORY. If you skip this, the board becomes stale and misleading.
+> **NEVER exit with issue still in `in_progress`.** Always run `viban review $ISSUE_ID` before exiting — whether completed or stopped early.
 
 ## CLI Reference
 

package/commands/parallel-assign.md

@@ -0,0 +1,15 @@
+---
+description: "Assign and resolve multiple independent backlog issues in parallel using git worktrees and coordinated agents"
+---
+
+Run `/viban:parallel-assign` to process multiple backlog issues simultaneously.
+
+Usage: `/viban:parallel-assign [count]`
+
+- `count`: Number of issues to process in parallel (default: 3, max: 5)
+
+Examples:
+- `/viban:parallel-assign` — resolve up to 3 backlog issues in parallel
+- `/viban:parallel-assign 5` — resolve up to 5 backlog issues in parallel
+
+Each issue gets its own opus agent working in an isolated git worktree. After all agents finish, PRs are created, local branches are preserved, and worktrees are cleaned up.

package/commands/sync.md

@@ -16,7 +16,7 @@ Sync the viban board with an external issue tracker. Currently supports GitHub I
 
 ```bash
 # Check if sync is already configured
-if [ -f "$(git rev-parse --git-common-dir 2>/dev/null || echo .viban)/sync.json" ]; then
+if [ -f ".viban/sync.json" ]; then
     echo "Sync configured"
     viban sync --status
 else

package/docs/CLAUDE.md

@@ -285,12 +285,11 @@ viban help              # Show help
 
 ### Data Location
 
-Issues are stored in `viban.json` at the git common directory:
+Issues are stored in `viban.json` in the `.viban/` directory:
 
 ```bash
-# Find viban.json
-git rev-parse --git-common-dir
-# → .git/viban.json (or ../../.git/viban.json in worktrees)
+# Default location
+.viban/viban.json
 ```
 
 **Custom location:**

package/package.json

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

package/scripts/providers/github.sh

@@ -130,7 +130,7 @@ provider_fetch_issues() {
     local repo="$1"
 
     local issues
-    issues=$(gh issue list --repo "$repo" --state open --json number,title,body,labels,updatedAt --limit 200 2>/dev/null) || {
+    issues=$(gh issue list --repo "$repo" --state all --json number,title,body,labels,state,updatedAt --limit 200 2>/dev/null) || {
         echo "Error: Failed to fetch issues from $repo"
         return 1
     }
@@ -141,7 +141,8 @@ provider_fetch_issues() {
         title: .title,
         description: (.body // ""),
         status: (
-            if ([.labels[].name] | any(. == "review")) then "review"
+            if .state == "closed" then "done"
+            elif ([.labels[].name] | any(. == "review")) then "review"
             elif ([.labels[].name] | any(. == "in-progress")) then "in_progress"
             else "backlog"
             end

package/scripts/sync.sh

@@ -149,7 +149,12 @@ sync_pull() {
             '.issues[] | select(.external_id == $eid)' "$VIBAN_JSON" 2>/dev/null)
 
         if [[ -z "$viban_card" || "$viban_card" == "null" ]]; then
-            # New remote issue -> import
+            # New remote issue -> import (skip already-closed issues)
+            if [[ "$status" == "done" ]]; then
+                echo "  == ${ext_id} \"${title}\" (closed, skipped)"
+                ((unchanged++))
+                continue
+            fi
             if [[ "$dry_run" == "true" ]]; then
                 echo "  <- ${ext_id} \"${title}\" (new card to create)"
             else
@@ -189,6 +194,24 @@ sync_pull() {
             viban_id=$(echo "$viban_card" | jq -r '.id')
             viban_updated=$(echo "$viban_card" | jq -r '.updated_at')
 
+            # Remote issue closed -> remove card from viban
+            if [[ "$status" == "done" ]]; then
+                if [[ "$dry_run" == "true" ]]; then
+                    echo "  <- ${ext_id} \"${title}\" (closed remotely, will remove card)"
+                else
+                    jq --argjson id "$viban_id" 'del(.issues[]|select((.id|tonumber)==$id))' \
+                        "$VIBAN_JSON" > "${VIBAN_JSON}.tmp" && mv "${VIBAN_JSON}.tmp" "$VIBAN_JSON"
+                    # Remove sync metadata for this card
+                    local meta_tmp
+                    meta_tmp=$(read_sync_meta)
+                    meta_tmp=$(echo "$meta_tmp" | jq --arg vid "$viban_id" 'del(.issues[$vid])')
+                    write_sync_meta "$meta_tmp"
+                    echo "  <- ${ext_id} \"${title}\" (closed remotely, card removed)"
+                fi
+                ((pulled++))
+                continue
+            fi
+
             # Get last known sync timestamps
             local meta
             meta=$(get_issue_meta "$viban_id")
@@ -461,6 +484,7 @@ main() {
     local push_new=false
     local pull_only=false
     local push_only=false
+    local auto_mode=false
     local repo_override=""
 
     while [[ $# -gt 0 ]]; do
@@ -471,6 +495,7 @@ main() {
             --push-new)  push_new=true; shift ;;
             --pull-only) pull_only=true; shift ;;
             --push-only) push_only=true; shift ;;
+            --auto)      auto_mode=true; shift ;;
             --repo)      repo_override="$2"; shift 2 ;;
             --provider)  shift 2 ;;  # Already handled by bin/viban
             *)           echo "Unknown option: $1"; exit 1 ;;
@@ -515,6 +540,18 @@ main() {
         exit 1
     fi
 
+    # Auto mode: silent pull-only for TUI background use
+    if [[ "$auto_mode" == "true" ]]; then
+        sync_pull "$repo" false >/dev/null 2>&1
+        local now
+        now=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+        local meta
+        meta=$(read_sync_meta)
+        meta=$(echo "$meta" | jq --arg now "$now" '.last_sync_at = $now')
+        write_sync_meta "$meta"
+        exit 0
+    fi
+
     # Execute sync
     if [[ "$pull_only" == "true" ]]; then
         echo "Pulling from $(provider_name) ($repo)..."

package/scripts/sync_create.sh

@@ -0,0 +1,68 @@
+#!/bin/bash
+# viban sync_create - Create a remote issue from a viban card
+# Called by cmd_add when sync is configured.
+#
+# Usage: sync_create.sh <card_id>
+# Output: external_id string (e.g., "github:42") on success, empty on failure
+#
+# Environment variables (set by caller):
+#   VIBAN_JSON       - Path to viban.json
+#   VIBAN_DATA_DIR   - Path to viban data directory
+#   VIBAN_PROVIDER   - Provider name (e.g., "github")
+#   VIBAN_SCRIPT_DIR - Path to viban install directory
+
+set -euo pipefail
+
+card_id="$1"
+SYNC_JSON="${VIBAN_DATA_DIR}/sync.json"
+PROVIDER_SCRIPT="${VIBAN_SCRIPT_DIR}/scripts/providers/${VIBAN_PROVIDER}.sh"
+
+# Load provider
+if [[ ! -f "$PROVIDER_SCRIPT" ]]; then
+    exit 1
+fi
+source "$PROVIDER_SCRIPT"
+
+# Read card from viban.json
+card=$(jq --argjson id "$card_id" '.issues[] | select((.id|tonumber)==$id)' "$VIBAN_JSON" 2>/dev/null) || exit 1
+if [[ -z "$card" || "$card" == "null" ]]; then exit 1; fi
+
+# Get repo from sync config
+repo=$(jq -r '.provider_config.repo' "$SYNC_JSON" 2>/dev/null) || exit 1
+if [[ -z "$repo" || "$repo" == "null" ]]; then exit 1; fi
+
+# Check provider auth (silent)
+provider_check_deps &>/dev/null || exit 1
+provider_check_auth &>/dev/null || exit 1
+
+# Create remote issue (split pipeline to avoid SIGPIPE with pipefail)
+issue_json=$(echo "$card" | jq '{
+    title: .title,
+    description: (.description // ""),
+    status: .status,
+    priority: (.priority // "P3"),
+    type: (.type // "")
+}') || exit 1
+new_remote_id=$(echo "$issue_json" | provider_create_issue "$repo" 2>/dev/null) || exit 1
+
+if [[ -z "$new_remote_id" ]]; then exit 1; fi
+
+# Build external_id
+provider_prefix="$(provider_name):"
+ext_id="${provider_prefix}${new_remote_id}"
+
+# Update card with external_id
+now=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+jq --argjson vid "$card_id" --arg eid "$ext_id" --arg now "$now" \
+    '(.issues[] | select((.id|tonumber)==$vid)) |= . + {external_id: $eid, updated_at: $now}' \
+    "$VIBAN_JSON" > "${VIBAN_JSON}.tmp" && mv "${VIBAN_JSON}.tmp" "$VIBAN_JSON"
+
+# Record sync metadata
+sync_meta=$(cat "$SYNC_JSON")
+sync_meta=$(echo "$sync_meta" | jq --arg vid "$card_id" --arg rid "$new_remote_id" \
+    --arg now "$now" \
+    '.issues[$vid] = {remote_id: $rid, remote_updated_at: $now, viban_updated_at: $now}')
+echo "$sync_meta" > "${SYNC_JSON}.tmp" && mv "${SYNC_JSON}.tmp" "$SYNC_JSON"
+
+# Output external_id for caller
+echo "$ext_id"

package/skills/add/SKILL.md

@@ -5,78 +5,54 @@ description: "Register a problem as a viban issue"
 
 # /add - Register Issue
 
-Register a problem as a viban issue. Keep it lightweight — no codebase exploration, no heavy analysis.
+Register a problem as a viban issue. No codebase exploration, no solutions — symptoms only.
 
-> **Principle**: Clarify symptoms only if vague. Don't explore code or propose solutions.
+**Input**: `$ARGUMENTS`
 
-## Input
+## Step 1: Clarify (only if vague)
 
-**User Input**: `$ARGUMENTS`
+If clear enough (who/what/where), skip to Step 2. Otherwise, one AskUserQuestion:
+- header: "Problem", question: "Can you describe the symptom more specifically?"
+- options: context-appropriate (e.g. "Error/crash", "Feature not working", "Performance issue", "Let me describe")
 
-## Step 1: Clarify (only if needed)
+## Step 2: Priority & Type
 
-If the user's description is **clear enough** to register (who/what/where), skip to Step 2.
+Infer from description. Don't ask unless truly ambiguous.
 
-If **vague or ambiguous**, concretize with one AskUserQuestion:
+| Priority | Condition | Type | When |
+|----------|-----------|------|------|
+| P0 | System down, data loss | bug | Something broken |
+| P1 | Feature broken, errors | feat | New functionality |
+| P2 | Performance, warnings | chore | Maintenance, config |
+| P3 | Improvements, refactoring | refactor | Code restructuring |
 
-- header: "Problem"
-- question: "Can you describe the symptom more specifically?"
-- options based on context, e.g.:
-  - "Error/crash on specific action"
-  - "Feature not working as expected"
-  - "Performance issue"
-  - "Let me describe"
-- multiSelect: false
-
-Goal: get a **one-sentence symptom** clear enough for an assignee to understand.
-
-## Step 2: Determine Priority & Type
-
-Infer from the description. Do NOT ask unless truly ambiguous.
-
-| Condition | Priority |
-|-----------|----------|
-| System down, data loss | P0 |
-| Feature broken, errors | P1 |
-| Performance, warnings | P2 |
-| Improvements, refactoring | P3 |
-
-| Type | When |
-|------|------|
-| bug | Something is broken |
-| feat | New functionality |
-| chore | Maintenance, config |
-| refactor | Code restructuring |
-
-## Step 3: Check Workflow for Issue Numbering
+## Step 3: Issue Numbering
 
 ```bash
 [ -f ".viban/workflow.md" ] && cat ".viban/workflow.md"
 ```
 
-- If workflow says **Manual** issue numbering → ask user for an external ID (e.g. `PROJ-42`)
-- If workflow says **Auto** or no workflow exists → let viban auto-assign
-- If user provided a specific ID in `$ARGUMENTS` → use it regardless of workflow
+- Workflow says **Manual** → ask user for external ID (e.g. `PROJ-42`)
+- **Auto** or no workflow → let viban auto-assign
+- ID in `$ARGUMENTS` → use it regardless
 
 ## Step 4: Register
 
-Write the description to a temp file, then register:
-
 ```bash
 cat > /tmp/viban-desc.md <<'VIBAN_EOF'
 ## Symptoms
-{concretized one-sentence symptom from Step 1}
-{additional context from user input, if any}
+{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}
 
-# Manual numbering (when workflow specifies manual)
+# Manual numbering (when workflow specifies)
 viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type} --ext-id "{external_id}"
 ```
 
-**Why heredoc?** `<<'VIBAN_EOF'` prevents shell interpretation of backticks, `$`, etc.
+Use `<<'VIBAN_EOF'` (quoted) to prevent shell interpretation.
 
 ## Step 5: Report
 
@@ -87,9 +63,38 @@ Issue #{id} registered
   Status: backlog
 ```
 
-## Notes
+## Step 6: Suggest Plan Mode
+
+**Skip** for trivial issues (typo, one-liner config, simple copy edit).
+**Recommend** for everything else. Use AskUserQuestion:
+
+- header: "Next step", question: "Want to start planning the solution now?"
+- options:
+  - "Plan now (Recommended)" — 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.`
+
+**"Later"**: end skill.
+
+> **Bias towards planning.** When in doubt, suggest plan mode.
+
+## Rules
 
-- **No codebase exploration** — the assignee does that during `/viban:assign`
-- **No solution proposals** — focus on symptoms only
-- **Check duplicates** before registering: `viban list`
-- **Don't over-prioritize** — P0 is system-down only
+- No codebase exploration — assignee does that in `/viban:assign`
+- No solution proposals — symptoms only
+- Check duplicates first: `viban list`
+- P0 is system-down only