@cwim/kanban 1.1.7 → 1.1.9
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.
- package/README.md +3 -34
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,13 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
> Your AI's long-term memory. Visualized.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
**CWIM Kanban gives Claude Code a persistent memory layer.** It remembers what you were working on, recalls context automatically, and shows you everything on a live dashboard.
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
Ever ask Claude to "continue where we left off" and get a blank stare? That's because Claude has no memory between sessions. Every conversation starts fresh, and complex multi-step work gets lost.
|
|
10
|
-
|
|
11
|
-
CWIM Kanban fixes this by giving Claude a persistent task memory that survives across sessions.
|
|
7
|
+
No more "what were we doing again?" between sessions.
|
|
12
8
|
|
|
13
9
|
## How It Works
|
|
14
10
|
|
|
@@ -43,7 +39,7 @@ kanban
|
|
|
43
39
|
# Start the dashboard
|
|
44
40
|
kanban
|
|
45
41
|
|
|
46
|
-
# Add to your Claude Code MCP config (~/.claude/
|
|
42
|
+
# Add to your Claude Code MCP config (~/.claude/claude.json)
|
|
47
43
|
{
|
|
48
44
|
"mcpServers": {
|
|
49
45
|
"kanban": {
|
|
@@ -71,33 +67,6 @@ Use the cwim-kanban MCP to track all work in this project.
|
|
|
71
67
|
4. **Finishing**: Move to `done` and append a summary note
|
|
72
68
|
5. **Blocked**: Move to `blocked` with a note explaining why
|
|
73
69
|
|
|
74
|
-
### Example
|
|
75
|
-
```
|
|
76
|
-
// Check if we have existing context
|
|
77
|
-
task_recall({ context: "refactoring auth middleware" })
|
|
78
|
-
|
|
79
|
-
// Create or update task
|
|
80
|
-
task_create({
|
|
81
|
-
title: "Refactor auth middleware",
|
|
82
|
-
description: "Extract JWT validation into separate module",
|
|
83
|
-
status: "in-progress",
|
|
84
|
-
tags: ["refactor", "auth"]
|
|
85
|
-
})
|
|
86
|
-
|
|
87
|
-
// Append progress notes
|
|
88
|
-
task_append_note({
|
|
89
|
-
id: "tf-abc123",
|
|
90
|
-
note: "Discovered edge case with refresh tokens"
|
|
91
|
-
})
|
|
92
|
-
|
|
93
|
-
// Mark complete
|
|
94
|
-
task_move({ id: "tf-abc123", status: "done" })
|
|
95
|
-
task_append_note({
|
|
96
|
-
id: "tf-abc123",
|
|
97
|
-
note: "Completed: Extracted JWT validation, all tests passing"
|
|
98
|
-
})
|
|
99
|
-
```
|
|
100
|
-
|
|
101
70
|
### Rules
|
|
102
71
|
- Always check for existing tasks before creating new ones
|
|
103
72
|
- Use tags consistently (e.g., "bug", "feature", "refactor", "docs")
|