workflowy-triage 0.1.0 → 0.1.2

package/README.md

@@ -48,11 +48,11 @@ Each proposal looks like:
 
 ```
 [source node]
-├── [node name](id) -> [target name]
-│   ├── [original node] ← moved here
+├── "original node text..." -> [link to target location]
+│   ├── [original node]
 │   ├── target: [link to proposed location]
-│   ├── reason: [why this location fits]
-│   └── alternative targets: [other options]
+│   ├── reason: "why this location fits"
+│   └── alternative targets: [link to other locations]
 ```
 
 ### Phase 2: User Review
@@ -71,18 +71,16 @@ Run `/workflowy-triage <node-id> --review` to:
 
 ## Triage Rules
 
-Create a node called "rules for triage" in your Workflowy with patterns like:
+Create a node called "rules for triage" in your Workflowy with rules like:
 
 ```
 rules for triage
-├── AI/LLM insights → use agents
-├── actionable tasks → plan > in the next 7 days
-├── meeting notes → grow > grow understanding
-├── business opportunities → create a business
-└── philosophical insights → remember, ponder, reflect
+├── find the deepest most applicable node under synthesize
+├── before finalizing a location, always call workflowy_get on it to see its children
+│   └── only stop when the node is a leaf or no children match the item's content
 ```
 
-Claude will match items against these patterns and propose appropriate locations.
+Claude will start from broad categories and drill down recursively, fetching children at each level until finding the most specific matching location.
 
 ## Uninstall
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflowy-triage",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "type": "module",
   "description": "Claude Code skill that triages Workflowy nodes by proposing locations based on rules",
   "bin": {

package/skills/workflowy-triage/SKILL.md

@@ -138,7 +138,7 @@ For each node to triage:
 [inbox] ← source-node-id
 ├── science of achievement vs art of fulfillment
 ├── try get shit done plugin
-└── Ian (meeting notes about Maven Machines)
+└── John (meeting notes)
 ```
 
 ### After Phase 1
@@ -155,22 +155,22 @@ For each node to triage:
 │   ├── target: [in the next 7 days](link)
 │   ├── reason: actionable task to try a productivity tool
 │   └── alternative targets: [use skills](link)
-└── [Ian](c19f) -> [care for, mate, partner, invest]
-    ├── Ian (meeting notes about Maven Machines)
-    ├── target: [care for, mate, partner, invest](link)
+└── [John](c19f) -> [care for, partner, invest]
+    ├── John (meeting notes)
+    ├── target: [care for, partner, invest](link)
     ├── reason: developing a business relationship
     └── alternative targets: [grow understanding](link), [partner](link)
 ```
 
 ### After User Review
 
-User moved "Ian" under the alternative suggestion, deleted the primary. User accepted other suggestions.
+User moved "John" under the alternative suggestion, deleted the primary. User accepted other suggestions.
 
 ### Phase 3 Output
 
 ```
 Observed patterns:
-- You moved "Ian" to "grow > grow understanding" instead of "reproduce > care for..."
+- You moved "John" to "grow > grow understanding" instead of "reproduce > care for..."
 - This suggests meeting notes should prioritize learning over relationship-building
 
 Proposed rule update:
@@ -185,22 +185,16 @@ The rules node should contain children structured as:
 
 ```
 [rules for triage]
-├── links and references → metabolize > store > resources
-├── philosophical insights → respond > remember, ponder, reflect
-├── actionable tasks → plan > in the next 7 days
-├── meeting notes → grow > grow understanding, experience
-├── business relationships → reproduce > care for, mate, partner, invest
-├── technical research → create > research scientifically
-├── creative production → create > create
-├── attention/focus principles → structure > attend to, focus
-├── tool configurations → structure > know structure > things, objects
-└── customer interactions → reproduce > add to, foster, promote, empower
-```
-
-Each rule is a simple pattern → location mapping. Rules can include:
-- Keywords to match
-- Node structure patterns (e.g., "has children", "contains link")
-- Context hints
+├── find the deepest most applicable node under synthesize
+├── before finalizing a location, always call workflowy_get on it to see its children
+│   └── only stop when the node is a leaf or no children match the item's content
+```
+
+Each rule guides how to find the best location. The triage process should:
+1. Start from broad categories and drill down
+2. For each candidate location, fetch its children with `workflowy_get`
+3. Check if any child is a better match for the item's content
+4. Continue recursively until reaching a leaf node or no children match
 
 ## Error Handling