claude-plugin-viban 1.3.3 → 1.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/commands/add.md +25 -39
  3. package/commands/assign.md +2 -0
  4. package/package.json +1 -1
  5. package/skills/add/SKILL.md +23 -39
package/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "viban",
3
- "version": "1.3.3",
3
+ "version": "1.3.4",
4
4
  "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
5
5
  "author": {
6
6
  "name": "happy-nut"
package/commands/add.md CHANGED
@@ -2,6 +2,8 @@
2
2
  description: "Register a problem as a viban issue"
3
3
  ---
4
4
 
5
+ > Tip: Run `/clear` before `/viban:add` for a clean context.
6
+
5
7
  # /add - Register Issue
6
8
 
7
9
  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.
40
42
  ## Step 4: Register
41
43
 
42
44
  ```bash
43
- cat > /tmp/viban-desc.md <<'VIBAN_EOF'
45
+ mkdir -p .viban/tmp
46
+ cat > .viban/tmp/desc.md <<'VIBAN_EOF'
44
47
  ## Symptoms
45
48
  {one-sentence symptom}
46
49
  {additional context, if any}
47
50
  VIBAN_EOF
48
51
 
49
52
  # Auto numbering (default)
50
- viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type}
53
+ viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type}
54
+ rm -f .viban/tmp/desc.md
51
55
 
52
56
  # Manual numbering (when workflow specifies)
53
- viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type} --ext-id "{external_id}"
57
+ viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type} --ext-id "{external_id}"
58
+ rm -f .viban/tmp/desc.md
54
59
  ```
55
60
 
56
61
  Use `<<'VIBAN_EOF'` (quoted) to prevent shell interpretation.
@@ -64,49 +69,30 @@ Issue #{id} registered
64
69
  Status: backlog
65
70
  ```
66
71
 
67
- ## Step 6: Suggest Plan Mode
68
-
69
- **Skip** unless the issue clearly needs upfront design. Most issues don't.
70
-
71
- Only suggest plan mode when:
72
- - The issue spans multiple subsystems or requires architectural decisions
73
- - The description is too vague to act on without investigation
74
- - P0 issues where a wrong fix could make things worse
75
-
76
- **Do NOT suggest** for: single-file fixes, straightforward bugs, feature additions with clear scope, chores, refactors with obvious targets.
72
+ ## Step 6: Done
77
73
 
78
- When suggesting, use AskUserQuestion:
74
+ Report the registered issue and **stop immediately**. Do not suggest next steps, do not offer to plan, do not continue.
79
75
 
80
- - header: "Next step", question: "This looks complex — want to plan before working on it?"
81
- - options:
82
- - "Plan now" — Enter plan mode to analyze and design a solution
83
- - "Later" — Just register, work on it later
76
+ > **This skill ends here. No exceptions.**
84
77
 
85
- **"Plan now"**: `EnterPlanMode` → after approval, save to `.viban/plans/{issue-id}.md`:
86
-
87
- ```bash
88
- mkdir -p .viban/plans
89
- ```
90
-
91
- ```markdown
92
- # Plan: {issue title}
93
- > Issue #{id} | {priority} | {type} | Created: {timestamp}
94
-
95
- {full plan content}
96
- ```
97
-
98
- Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-load it.`
78
+ ## Rules
99
79
 
100
- **"Later"**: end skill.
80
+ ### READ-ONLY MODE — This skill must NOT modify any files.
101
81
 
102
- > **Bias towards skipping.** When in doubt, just register and finish.
82
+ **Allowed tools (whitelist — everything else is FORBIDDEN):**
83
+ - `Bash`: ONLY for `mkdir -p .viban/tmp`, `viban add`, `viban list`, `cat .viban/workflow.md`, `rm -f .viban/tmp/desc.md`
84
+ - `Write`: ONLY for `.viban/tmp/desc.md` (temp file for `--desc-file`)
85
+ - `AskUserQuestion`: for clarification
86
+ - `Read`: for reading `.viban/workflow.md`
103
87
 
104
- ## Rules
88
+ **FORBIDDEN tools and actions:**
89
+ - `Edit`: NEVER use. No file modifications of any kind.
90
+ - `Write` to any path outside `/tmp/viban-*.md` and `.viban/plans/`: FORBIDDEN.
91
+ - `Bash` for anything other than `viban` CLI and `cat`/`mkdir` above: FORBIDDEN.
92
+ - No `git` commands. No source code reads. No codebase exploration.
105
93
 
106
- - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban add`, `viban list`, etc.)
107
- - **NEVER edit, create, or modify any source code files** — this skill registers issues only
108
- - **NEVER start implementation** — even after plan mode, just save the plan and stop
109
- - No codebase exploration — assignee does that in `/viban:assign`
94
+ ### Additional rules:
95
+ - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands
110
96
  - No solution proposals in the issue — symptoms only
111
97
  - Check duplicates first: `viban list`
112
98
  - P0 is system-down only
package/commands/assign.md CHANGED
@@ -2,6 +2,8 @@
2
2
  description: "Assign first backlog issue — clarify if unclear, then finish"
3
3
  ---
4
4
 
5
+ > Tip: Run `/clear` before `/viban:assign` for a clean context.
6
+
5
7
  Run `/viban:assign` to pick up the next backlog issue.
6
8
 
7
9
  Usage: `/viban:assign`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-plugin-viban",
3
- "version": "1.3.3",
3
+ "version": "1.3.4",
4
4
  "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
5
5
  "main": "bin/viban",
6
6
  "bin": {
package/skills/add/SKILL.md CHANGED
@@ -41,17 +41,20 @@ Infer from description. Don't ask unless truly ambiguous.
41
41
  ## Step 4: Register
42
42
 
43
43
  ```bash
44
- cat > /tmp/viban-desc.md <<'VIBAN_EOF'
44
+ mkdir -p .viban/tmp
45
+ cat > .viban/tmp/desc.md <<'VIBAN_EOF'
45
46
  ## Symptoms
46
47
  {one-sentence symptom}
47
48
  {additional context, if any}
48
49
  VIBAN_EOF
49
50
 
50
51
  # Auto numbering (default)
51
- viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type}
52
+ viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type}
53
+ rm -f .viban/tmp/desc.md
52
54
 
53
55
  # Manual numbering (when workflow specifies)
54
- viban add "{title}" --desc-file /tmp/viban-desc.md --priority {priority} --type {type} --ext-id "{external_id}"
56
+ viban add "{title}" --desc-file .viban/tmp/desc.md --priority {priority} --type {type} --ext-id "{external_id}"
57
+ rm -f .viban/tmp/desc.md
55
58
  ```
56
59
 
57
60
  Use `<<'VIBAN_EOF'` (quoted) to prevent shell interpretation.
@@ -65,49 +68,30 @@ Issue #{id} registered
65
68
  Status: backlog
66
69
  ```
67
70
 
68
- ## Step 6: Suggest Plan Mode
71
+ ## Step 6: Done
69
72
 
70
- **Skip** unless the issue clearly needs upfront design. Most issues don't.
73
+ Report the registered issue and **stop immediately**. Do not suggest next steps, do not offer to plan, do not continue.
71
74
 
72
- Only suggest plan mode when:
73
- - The issue spans multiple subsystems or requires architectural decisions
74
- - The description is too vague to act on without investigation
75
- - P0 issues where a wrong fix could make things worse
75
+ > **This skill ends here. No exceptions.**
76
76
 
77
- **Do NOT suggest** for: single-file fixes, straightforward bugs, feature additions with clear scope, chores, refactors with obvious targets.
78
-
79
- When suggesting, use AskUserQuestion:
80
-
81
- - header: "Next step", question: "This looks complex — want to plan before working on it?"
82
- - options:
83
- - "Plan now" — Enter plan mode to analyze and design a solution
84
- - "Later" — Just register, work on it later
85
-
86
- **"Plan now"**: `EnterPlanMode` → after approval, save to `.viban/plans/{issue-id}.md`:
87
-
88
- ```bash
89
- mkdir -p .viban/plans
90
- ```
91
-
92
- ```markdown
93
- # Plan: {issue title}
94
- > Issue #{id} | {priority} | {type} | Created: {timestamp}
95
-
96
- {full plan content}
97
- ```
98
-
99
- Report: `Plan saved to .viban/plans/{issue-id}.md — /viban:assign will auto-load it.`
77
+ ## Rules
100
78
 
101
- **"Later"**: end skill.
79
+ ### READ-ONLY MODE — This skill must NOT modify any files.
102
80
 
103
- > **Bias towards skipping.** When in doubt, just register and finish.
81
+ **Allowed tools (whitelist — everything else is FORBIDDEN):**
82
+ - `Bash`: ONLY for `mkdir -p .viban/tmp`, `viban add`, `viban list`, `cat .viban/workflow.md`, `rm -f .viban/tmp/desc.md`
83
+ - `Write`: ONLY for `.viban/tmp/desc.md` (temp file for `--desc-file`)
84
+ - `AskUserQuestion`: for clarification
85
+ - `Read`: for reading `.viban/workflow.md`
104
86
 
105
- ## Rules
87
+ **FORBIDDEN tools and actions:**
88
+ - `Edit`: NEVER use. No file modifications of any kind.
89
+ - `Write` to any path outside `/tmp/viban-*.md` and `.viban/plans/`: FORBIDDEN.
90
+ - `Bash` for anything other than `viban` CLI and `cat`/`mkdir` above: FORBIDDEN.
91
+ - No `git` commands. No source code reads. No codebase exploration.
106
92
 
107
- - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban add`, `viban list`, etc.)
108
- - **NEVER edit, create, or modify any source code files** — this skill registers issues only
109
- - **NEVER start implementation** — even after plan mode, just save the plan and stop
110
- - No codebase exploration — assignee does that in `/viban:assign`
93
+ ### Additional rules:
94
+ - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands
111
95
  - No solution proposals in the issue — symptoms only
112
96
  - Check duplicates first: `viban list`
113
97
  - P0 is system-down only