claude-plugin-viban 1.3.8 → 1.3.11

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 (3) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/package.json +1 -1
  3. package/skills/assign/SKILL.md +19 -44
package/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "viban",
3
- "version": "1.3.8",
3
+ "version": "1.3.11",
4
4
  "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
5
5
  "author": {
6
6
  "name": "happy-nut"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-plugin-viban",
3
- "version": "1.3.8",
3
+ "version": "1.3.11",
4
4
  "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
5
5
  "main": "bin/viban",
6
6
  "bin": {
package/skills/assign/SKILL.md CHANGED
@@ -45,33 +45,12 @@ viban get $ISSUE_ID
45
45
 
46
46
  Display the issue title, description, priority, and type to the user.
47
47
 
48
- ## Step 3: Evaluate Clarity
48
+ ## Step 3: Evaluate Clarity → Proceed Immediately
49
49
 
50
- Assess whether the issue description provides enough context to start working:
50
+ Assess whether the issue description provides enough context to start working.
51
51
 
52
- - **Clear**: the symptom, affected area, and expected behavior are all understandable
53
- - **Unclear**: vague description, missing context, ambiguous scope, or multiple possible interpretations
54
-
55
- ### If Unclear
56
-
57
- Interview the user with AskUserQuestion to gather missing context. Ask about:
58
- - What specifically is the problem? (symptom)
59
- - Where does it happen? (location/trigger)
60
- - What is the expected behavior?
61
- - Any additional constraints or context?
62
-
63
- After gathering answers, update the issue description:
64
-
65
- ```bash
66
- cat > /tmp/viban-desc-update.md <<'VIBAN_EOF'
67
- {original description}
68
-
69
- ## Clarification
70
- {gathered context from interview}
71
- VIBAN_EOF
72
-
73
- # Re-add the issue with enriched description (edit via TUI or recreate)
74
- ```
52
+ - **Clear** → **proceed directly to Step 4. Do NOT ask the user for confirmation. Do NOT ask "should I start?". Just start.**
53
+ - **Unclear** → interview the user with AskUserQuestion to gather missing context, then proceed to Step 4 immediately.
75
54
 
76
55
  ## Step 4: Execute Workflow
77
56
 
@@ -90,9 +69,7 @@ Follow the workflow from Step 0. If no workflow was found, use this default pipe
90
69
  - Run build and tests to confirm the fix works
91
70
  - Verify no regressions
92
71
 
93
- ### 4.4 Ship (MANDATORY)
94
-
95
- Every step below is **required** unless the workflow explicitly says to stop earlier.
72
+ ### 4.4 Ship (MANDATORY — execute ALL 4 commands in sequence)
96
73
 
97
74
  ```bash
98
75
  # 1. Commit
@@ -102,7 +79,7 @@ git commit -m "fix: {description} (#$ISSUE_ID)"
102
79
  # 2. Push
103
80
  git push -u origin issue-$ISSUE_ID
104
81
 
105
- # 3. Create PR (REQUIRED — do NOT skip this)
82
+ # 3. Create PR (REQUIRED — do NOT skip)
106
83
  gh pr create --title "fix: {description}" --body "Resolves #$ISSUE_ID
107
84
 
108
85
  ## Summary
@@ -110,19 +87,18 @@ gh pr create --title "fix: {description}" --body "Resolves #$ISSUE_ID
110
87
 
111
88
  ## Test plan
112
89
  {how it was verified}"
113
- ```
114
-
115
- **If `gh pr create` fails**: fix the error and retry. Do NOT skip PR creation.
116
-
117
- ## Step 5: Move to Review
118
90
 
119
- After PR is created:
120
-
121
- ```bash
91
+ # 4. Move to review (REQUIRED — do NOT skip)
122
92
  viban review $ISSUE_ID
123
93
  ```
124
94
 
125
- Report completion with the PR URL:
95
+ **If any command fails**: fix the error and retry. Do NOT skip any step.
96
+
97
+ ### Completion Checklist (ALL must be true before you stop)
98
+
99
+ - [ ] PR created (you have a PR URL)
100
+ - [ ] `viban review` called (issue status is "review")
101
+ - [ ] Completion message includes PR URL
126
102
 
127
103
  ```
128
104
  Issue #{id} resolved → review
@@ -130,15 +106,16 @@ Issue #{id} resolved → review
130
106
  PR: {pr_url}
131
107
  ```
132
108
 
133
- **Do NOT report completion without a PR URL.**
109
+ **If you don't have a PR URL or haven't called `viban review`, you are NOT done. Go back and do it.**
134
110
 
135
111
  ---
136
112
 
137
113
  ## CRITICAL
138
114
 
139
- > - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban assign`, `viban get`, `viban list`, `viban done`, etc.)
115
+ > - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban assign`, `viban get`, `viban list`, etc.)
116
+ > - **FORBIDDEN: `viban done`** — do NOT use `viban done` or `viban done --remove`. Cards must go to review, not done.
140
117
  > - **MUST create a PR** via `gh pr create` unless the workflow explicitly says "stop before PR".
141
- > - **MUST call `viban review`** after PR creation. Do NOT finish without moving the issue to review.
118
+ > - **MUST call `viban review`** after PR creation. This is the ONLY way to finish. Do NOT use any other status change.
142
119
  > - **MUST include PR URL** in the completion report. No URL = not done.
143
120
 
144
121
  ## CLI Reference
@@ -147,6 +124,4 @@ Issue #{id} resolved → review
147
124
  |---------|-------------|
148
125
  | `viban assign [session]` | Assign issue |
149
126
  | `viban get <id>` | View issue |
150
- | `viban done <id>` | Mark as done (non-destructive) |
151
- | `viban done <id> --remove` | Delete card permanently |
152
- | `viban review [id]` | Move to review |
127
+ | `viban review [id]` | Move to review (use this to finish) |