jettypod 4.4.3 → 4.4.5

package/jettypod.js

@@ -86,7 +86,9 @@ function ensureJettypodGitignores() {
   const entriesToIgnore = [
     '.claude/session.md',
     '.jettypod-work/',
-    '.jettypod-trash/'
+    '.jettypod-trash/',
+    '.jettypod/*.db-shm',
+    '.jettypod/*.db-wal'
   ];
 
   // Add entries to .gitignore if not present

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jettypod",
-  "version": "4.4.3",
+  "version": "4.4.5",
   "description": "AI-powered development workflow manager with TDD, BDD, and automatic test generation",
   "main": "jettypod.js",
   "bin": {

package/skills-templates/epic-planning/SKILL.md

@@ -24,7 +24,7 @@ You'll receive context about the epic being planned. Review:
 
 **Check for existing features:**
 ```bash
-node jettypod.js backlog | grep -A 20 "Epic Name"
+jettypod backlog | grep -A 20 "Epic Name"
 ```
 
 If features already exist, acknowledge them and skip to Step 4 (Architectural Decision).
@@ -165,15 +165,15 @@ Use the Bash tool to create each feature. Replace `<EPIC_ID>` with the actual ep
 
 ```javascript
 // CORRECT - uses actual numeric epic ID:
-node jettypod.js work create feature "Live cursor tracking" "Track cursor positions in real-time" --parent=5
+jettypod work create feature "Live cursor tracking" "Track cursor positions in real-time" --parent=5
 
 // WRONG - missing parent flag (feature won't be under epic):
-node jettypod.js work create feature "Live cursor tracking" "Track cursor positions in real-time"
+jettypod work create feature "Live cursor tracking" "Track cursor positions in real-time"
 ```
 
 For each feature, execute:
 ```bash
-node jettypod.js work create feature "<Title>" "<Description>" --parent=<EPIC_ID>
+jettypod work create feature "<Title>" "<Description>" --parent=<EPIC_ID>
 ```
 
 Display to user as you create each one:
@@ -203,7 +203,7 @@ Does this rationale capture why you chose this approach? (You can edit it if nee
 
 ```javascript
 // Use Bash tool to execute:
-node jettypod.js work epic-implement [epic-id] \
+jettypod work epic-implement [epic-id] \
   --aspect="Architecture" \
   --decision="[architectural approach chosen]" \
   --rationale="[user's confirmed/edited rationale]"

package/skills-templates/external-transition/SKILL.md

@@ -335,7 +335,7 @@ Wait for final "yes" confirmation.
 Only after receiving explicit "yes" confirmation, execute the transition using the Bash tool:
 
 ```bash
-node jettypod.js project external
+jettypod project external
 ```
 
 ### Step 10: Report Results

package/skills-templates/feature-planning/SKILL.md

@@ -427,7 +427,7 @@ Does this rationale capture why you chose this approach? (You can edit it if nee
 
 ```bash
 # Use Bash tool to execute:
-node jettypod.js work implement [feature-id] \
+jettypod work implement [feature-id] \
   --winner="[approach-name or prototypes/winner-file]" \
   --rationale="[user's confirmed/edited rationale]"
 ```
@@ -442,7 +442,7 @@ For each chore that the user confirmed in Step 7, use the Bash tool to create it
 
 ```bash
 # Use Bash tool to execute for each chore:
-node jettypod.js work create chore "[Chore title]" "[Chore description with all the implementation guidance]" --parent=[feature-id]
+jettypod work create chore "[Chore title]" "[Chore description with all the implementation guidance]" --parent=[feature-id]
 ```
 
 **Build the description from your Step 7 proposal:**

package/skills-templates/speed-mode/SKILL.md

@@ -199,16 +199,16 @@ Speed mode is ONLY a checkpoint to prove functionality works. Features are INCOM
 **Required workflow after speed mode implementation:**
 
 1. ✅ **Complete ALL speed mode chores** - Implement all success scenarios (required + optional features)
-2. ✅ **Elevate to stable mode** - Use `node jettypod.js work set-mode <feature-id> stable` to auto-generate stable mode chores
+2. ✅ **Elevate to stable mode** - Use `jettypod work set-mode <feature-id> stable` to auto-generate stable mode chores
 3. ✅ **Implement stable mode chores** - Add error handling and edge cases
 4. ❌ **NEVER mark feature complete in speed mode** - This bypasses critical quality gates
 
 **If you attempt to mark a feature complete while in speed mode, the system will block you with an error.**
 
 The validation will require you to:
-- Elevate to stable mode: `node jettypod.js work set-mode <feature-id> stable`
+- Elevate to stable mode: `jettypod work set-mode <feature-id> stable`
 - This will automatically analyze the implementation and generate appropriate stable mode chores
-- Or explicitly skip (not recommended): `node jettypod.js work set-mode <feature-id> stable --force`
+- Or explicitly skip (not recommended): `jettypod work set-mode <feature-id> stable --force`
 
 **Remember:** Speed mode makes it work (all success scenarios). Stable mode makes it robust (handles failures).
 

package/skills-templates/stable-mode/SKILL.md

@@ -549,7 +549,7 @@ grep -A1 "<project_state>" "$(git rev-parse --show-toplevel)/CLAUDE.md" | tail -
 
 Mark the feature as done:
 ```bash
-node jettypod.js work status [feature-id] done
+jettypod work status [feature-id] done
 ```
 
 Display: