jettypod 4.4.94 → 4.4.96

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

@@ -30,12 +30,72 @@ When this skill is activated, you are helping implement a production mode chore
 
 ---
 
+## 🛑 PRE-FLIGHT VALIDATION (REQUIRED)
+
+**Before proceeding with ANY implementation, you MUST validate the worktree exists.**
+
+Run this query FIRST:
+
+```bash
+sqlite3 .jettypod/work.db "SELECT wi.id, wi.title, wi.status, wt.worktree_path, wt.branch_name FROM work_items wi LEFT JOIN worktrees wt ON wi.id = wt.work_item_id WHERE wi.status = 'in_progress' AND wi.type = 'chore'"
+```
+
+**Check the result:**
+
+| worktree_path | What it means | Action |
+|---------------|---------------|--------|
+| **Has a path** (e.g., `/path/to/.jettypod-work/...`) | ✅ Worktree exists, ready to proceed | Continue to Step 0 |
+| **NULL or empty** | ❌ `work start` was not called | **STOP - run `jettypod work start [chore-id]` first** |
+| **No rows returned** | ❌ No chore is in progress | **STOP - verify the chore exists and run `work start`** |
+
+**🛑 STOP GATE:** If `worktree_path` is NULL or no rows returned, you MUST run `jettypod work start [chore-id]` before continuing. DO NOT proceed without a valid worktree.
+
+**🚫 FORBIDDEN: Manual Git Worktree Commands**
+```
+❌ git worktree add ...
+❌ git checkout -b feature/...
+❌ git branch feature/...
+```
+**ALWAYS use `jettypod work start`** - it handles branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
+
+---
+
+## 🔒 WORKTREE PATH LOCK
+
+**After pre-flight validation passes, capture and lock the worktree path:**
+
+From the pre-flight query output, extract and store:
+- `WORKTREE_PATH` - the absolute path to the worktree
+
+**Display:**
+
+```
+🔒 WORKTREE LOCK ACTIVE
+Path: ${WORKTREE_PATH}
+
+All file writes will use this path.
+```
+
+**From this point forward, ALL file operations MUST use paths starting with `${WORKTREE_PATH}/`**
+
+This lock prevents accidental writes to the main repository.
+
+---
+
 ## Implementation Steps
 
 ### Step 0: Detect Production Context (CRITICAL FIRST STEP)
 
 **MUST RUN FIRST:** Detect which scenario applies to this feature.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a DETECTION step.** File writes happen in Step 3.
+
 **To detect context, check these conditions:**
 
 ```bash
@@ -89,6 +149,14 @@ This validates that `stable_mode_complete` gate is passed and creates an executi
 
 **For all scenarios:** Read production standards file.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a READ step.** File writes happen in Step 3.
+
 ```bash
 # Check if production standards file exists
 ls .jettypod/production-standards.json
@@ -111,6 +179,14 @@ jettypod workflow checkpoint <feature-id> --step=1
 
 **For Scenario A only:** Quick validation of existing scenarios.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a VALIDATION step.** File writes happen in Step 3.
+
 ```javascript
 const { validateScenarios } = require('../../lib/production-scenario-validator');
 const { getDb } = require('../../lib/database');
@@ -168,6 +244,14 @@ try {
 
 **For Scenario B only:** Re-validate with current standards.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a VALIDATION step.** File writes happen in Step 3.
+
 ```javascript
 const { validateScenarios } = require('../../lib/production-scenario-validator');
 const config = require('../../lib/config');
@@ -223,6 +307,14 @@ try {
 
 **For Scenario C only:** Generate production scenarios from standards.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a GENERATION step (via jettypod commands, not direct file writes).** File writes happen in Step 3.
+
 ```bash
 # Get feature details
 sqlite3 .jettypod/work.db "SELECT id, title, scenario_file FROM work_items WHERE id = <feature-id>"
@@ -247,6 +339,10 @@ jettypod workflow checkpoint <feature-id> --step=2
 
 ### Step 3: Implement Production Chore
 
+**🔒 WORKTREE PATH REQUIRED:** All file writes MUST use the `WORKTREE_PATH` captured after pre-flight validation.
+
+**✅ NOW you may write files** - worktree is locked, context is detected.
+
 **For all scenarios:** Implement the current production chore with test-driven iteration.
 
 **Get current work and identify target scenario:**

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

@@ -102,6 +102,28 @@ sqlite3 .jettypod/work.db "SELECT wi.id, wi.title, wi.status, wt.worktree_path,
 
 ---
 
+## 🔒 WORKTREE PATH LOCK
+
+**After pre-flight validation passes, capture and lock the worktree path:**
+
+From the pre-flight query output, extract and store:
+- `WORKTREE_PATH` - the absolute path to the worktree (e.g., `/path/to/.jettypod-work/4-add-nav-link`)
+
+**Display:**
+```
+🔒 WORKTREE LOCK ACTIVE
+Path: ${WORKTREE_PATH}
+
+All file writes will use this path.
+```
+
+**From this point forward, ALL file operations MUST use paths starting with:**
+```
+${WORKTREE_PATH}/
+```
+
+---
+
 ### Overview
 
 **Speed Mode Goal:** Make it work - implement ALL functionality (integration + required + optional features) to make success scenarios pass, assuming everything works correctly.
@@ -269,6 +291,14 @@ Analyzing BDD scenarios to determine implementation approach...
 
 ### Step 1: Check for Breadcrumbs and Analyze Scenario
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is an ANALYSIS step.** File writes happen in Step 5.
+
 **CRITICAL:** Claude Code executes this autonomously - no user permission needed.
 
 **Your task:**
@@ -340,6 +370,14 @@ Now analyzing codebase to propose implementation...
 
 ### Step 2: Autonomous Codebase Analysis
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is an ANALYSIS step.** File writes happen in Step 5.
+
 **CRITICAL:** Claude Code executes this autonomously - no user permission needed.
 
 **Your task:**
@@ -416,6 +454,14 @@ jettypod workflow checkpoint <feature-id> --step=2
 
 ### Step 3: Decide if Confirmation Needed
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a DECISION step.** File writes happen in Step 5.
+
 **Evaluate if you need user confirmation before implementing:**
 
 **Skip confirmation (proceed directly to Step 4) if:**
@@ -432,6 +478,14 @@ jettypod workflow checkpoint <feature-id> --step=2
 
 ### Step 3A: Propose Implementation Approach (Conditional)
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a PROPOSAL step.** File writes happen in Step 5.
+
 **⚡ ASYNC BOUNDARY - Only execute this if confirmation needed**
 
 **Present your analysis and proposal to the user:**
@@ -514,6 +568,10 @@ jettypod workflow checkpoint <feature-id> --step=4
 
 ### Step 5: RED→GREEN→REFACTOR Loop
 
+**🔒 WORKTREE PATH REQUIRED:** All file writes MUST use the `WORKTREE_PATH` captured after pre-flight validation.
+
+**✅ NOW you may write files** - worktree is locked, approach is confirmed.
+
 **Execute autonomously** - iterate until tests pass (max 10 iterations).
 
 **Each iteration (True TDD):**
@@ -862,7 +920,7 @@ cd <main-repo>                           # Bash call 1
 ```
 
 ```bash
-jettypod work merge --release-lock       # Bash call 2
+jettypod work merge <last-chore-id> --release-lock   # Bash call 2
 ```
 
 **🔄 WORKFLOW COMPLETE: Speed mode finished**
@@ -967,11 +1025,10 @@ Before ending speed-mode skill, ensure:
 cd <main-repo>
 ```
 ```bash
-# Bash call 2: Merge (pick one)
-jettypod work merge <id>               # Merge chore by ID (recommended)
-jettypod work merge                    # Merge current chore
-jettypod work merge --with-transition  # Hold lock for transition
-jettypod work merge --release-lock     # Release held lock
+# Bash call 2: Merge (ALWAYS include chore ID)
+jettypod work merge <chore-id>                    # Merge chore by ID
+jettypod work merge <chore-id> --with-transition  # Hold lock for transition
+jettypod work merge <chore-id> --release-lock     # Release held lock
 ```
 
 **Start chores:**

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

@@ -109,6 +109,28 @@ sqlite3 .jettypod/work.db "SELECT wi.id, wi.title, wi.status, wt.worktree_path,
 
 ---
 
+## 🔒 WORKTREE PATH LOCK
+
+**After pre-flight validation passes, capture and lock the worktree path:**
+
+From the pre-flight query output, extract and store:
+- `WORKTREE_PATH` - the absolute path to the worktree
+
+**Display:**
+
+```
+🔒 WORKTREE LOCK ACTIVE
+Path: ${WORKTREE_PATH}
+
+All file writes will use this path.
+```
+
+**From this point forward, ALL file operations MUST use paths starting with `${WORKTREE_PATH}/`**
+
+This lock prevents accidental writes to the main repository.
+
+---
+
 ### Overview
 
 **Stable Mode Goal:** Transform speed mode's "make it work" implementation into robust, reliable code with comprehensive error handling and validation.
@@ -271,6 +293,14 @@ Analyzing stable mode BDD scenarios to determine what error handling and validat
 
 **CRITICAL:** Claude Code executes this autonomously - no user permission needed.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is an ANALYSIS step.** File writes happen in Step 5.
+
 **Your task:**
 1. Get current work item and parent feature's scenario file
 2. Read the full scenario file (should have success scenarios + stable mode error/edge case scenarios)
@@ -328,6 +358,14 @@ Now reviewing speed mode implementation...
 
 **CRITICAL:** Claude Code executes this autonomously - no user permission needed.
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is an ANALYSIS step.** File writes happen in Step 5.
+
 **Your task:**
 1. Find files created/modified in speed mode
 2. Read the existing implementation
@@ -380,6 +418,14 @@ jettypod workflow checkpoint <feature-id> --step=2
 
 ### Step 3: Decide if Confirmation Needed
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a DECISION step.** File writes happen in Step 5.
+
 **Evaluate if you need user confirmation before implementing:**
 
 **Skip confirmation (proceed directly to Step 4) if:**
@@ -398,6 +444,14 @@ jettypod workflow checkpoint <feature-id> --step=2
 
 **⚡ ASYNC BOUNDARY - Only execute this if confirmation needed**
 
+**🚫 FORBIDDEN: Writing Files at This Step**
+```
+❌ Write tool to any path
+❌ Edit tool to any path
+❌ Any file creation or modification
+```
+**This is a PROPOSAL step.** File writes happen in Step 5.
+
 **Present your analysis and proposal to the user:**
 
 ```
@@ -496,6 +550,10 @@ jettypod workflow checkpoint <feature-id> --step=4
 
 ### Step 5: RED→GREEN→REFACTOR Loop
 
+**🔒 WORKTREE PATH REQUIRED:** All file writes MUST use the `WORKTREE_PATH` captured after pre-flight validation.
+
+**✅ NOW you may write files** - worktree is locked, approach is confirmed.
+
 **Execute autonomously** - iterate until tests pass (max 10 iterations).
 
 **Each iteration (True TDD):**
@@ -779,9 +837,8 @@ Before ending stable-mode skill, ensure:
 cd <main-repo>
 ```
 ```bash
-# Bash call 2: Merge (pick one)
-jettypod work merge <id>   # Merge chore by ID (recommended)
-jettypod work merge        # Merge current chore
+# Bash call 2: Merge (ALWAYS include chore ID)
+jettypod work merge <chore-id>   # Merge chore by ID
 ```
 
 **Start chores:**
@@ -811,7 +868,7 @@ jettypod work set-mode <feature-id> production  # Set feature to production mode
 - Parallel worktrees branch from main independently
 
 **Process:**
-1. Complete chore → run `cd <main-repo>` then `jettypod work merge` as SEPARATE Bash calls
+1. Complete chore → run `cd <main-repo>` then `jettypod work merge <chore-id>` as SEPARATE Bash calls
 2. Start next chore → `jettypod work start <next-id>`
 3. Repeat