@datatamer.ai/agentdev 1.0.1 → 1.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@datatamer.ai/agentdev",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "AgentDev distributed agent client for processing GitHub tickets",
   "type": "module",
   "main": "src/index.js",

package/skills/auto-ticket-workflow.md

@@ -66,6 +66,27 @@ fi
 - The most recent human comment takes priority over earlier instructions
 - If a comment says to stop or cancel, halt the workflow and comment on the issue
 
+## Check for Chat Messages Between Phases
+
+**Between every phase transition**, also check for direct chat messages:
+
+```bash
+if [ -f "$CHAT_SIGNAL_FILE" ]; then
+  echo "💬 Chat messages received!"
+  cat "$CHAT_SIGNAL_FILE"
+  rm "$CHAT_SIGNAL_FILE"
+  # Respond to each [conv:ID] message by writing JSON lines to CHAT_RESPONSE_FILE
+  # echo '{"conversation_id": <id>, "content": "your response"}' >> "$CHAT_RESPONSE_FILE"
+fi
+```
+
+**Rules:**
+- Use `>>` (append) when writing to `$CHAT_RESPONSE_FILE`
+- Each line must be a valid JSON object: `{"conversation_id": <int>, "content": "<response>"}`
+- Respond in context of your current work phase and progress
+- Always respond — never ignore chat messages
+- Keep responses concise but helpful
+
 ## GitHub Project Configuration
 
 ```
@@ -149,7 +170,7 @@ cat /tmp/gh-items.json | jq -r '.data.organization.projectV2.items.nodes[] | sel
 | **Todo** | Proceed to Phase 1 (Discovery & Claim) |
 | **Not on board** | Proceed to Phase 1 (Discovery & Claim) |
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 1: Ticket Discovery & Claim
 
@@ -175,7 +196,7 @@ If ticket found, extract and store:
 - `title`: Third field
 - `repo`: Fourth field (e.g., data-tamer-dashboard)
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 2: OpenSpec Creation (INLINED - NO Skill tool)
 
@@ -237,7 +258,7 @@ Starting automated implementation.
 
 **After Phase 2: Print "✓ OpenSpec artifacts created. CONTINUING TO PHASE 3..." and IMMEDIATELY proceed.**
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 3: Implementation (INLINED - NO Skill tool)
 
@@ -292,7 +313,7 @@ Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
 
 **After Phase 3: Print "✓ Implementation complete. CONTINUING TO PHASE 4..." and IMMEDIATELY proceed.**
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 4: Local Testing
 
@@ -315,7 +336,7 @@ Screenshots are saved to `/tmp/auto-ticket-screenshots/`
 
 **After Phase 4: Print "✓ Local tests passed. CONTINUING TO PHASE 5..." and IMMEDIATELY proceed.**
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 5: Production Deployment
 
@@ -342,7 +363,7 @@ ssh root@153.92.127.95 'export KUBECONFIG=/etc/rancher/k3s/k3s.yaml && kubectl g
 
 **After Phase 5: Print "✓ Production deployed. CONTINUING TO PHASE 6..." and IMMEDIATELY proceed.**
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 6: Production Testing
 
@@ -380,7 +401,7 @@ node playwright-test.js slides --production
    - Comment on issue confirming success
    - Print "✓ Production tests passed. CONTINUING TO PHASE 7..."
 
-**Before continuing, check for new comments** (see "Check for New Comments Between Phases" above).
+**Before continuing, check for new comments and chat messages** (see "Check for New Comments Between Phases" and "Check for Chat Messages Between Phases" above).
 
 ### Phase 7: Completion