jettypod 4.4.45 → 4.4.47

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

@@ -627,22 +627,42 @@ After merge, you are on main branch. Ready to generate stable mode scenarios.
 
 **⚡ ASYNC BOUNDARY - Must wait for user confirmation**
 
-**1. Read the feature's scenario file and analyze for stable mode needs:**
+**1. Create a test worktree for writing stable mode scenarios:**
+
+**🚫 FORBIDDEN: Manual Git Worktree Commands**
+```
+❌ git worktree add ...
+❌ git checkout -b tests/...
+❌ git branch tests/...
+```
+**ALWAYS use jettypod commands** - they handle branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
+
+```bash
+jettypod work tests <feature-id>
+```
+
+This creates an isolated worktree at `.jettypod-work/tests-<id>-<slug>` with branch `tests/feature-<id>-<slug>`.
+
+**🛑 CRITICAL:** All BDD file operations MUST use absolute paths in the test worktree:
+- ✅ `/path/to/.jettypod-work/tests-42-login/features/login.feature`
+- ❌ `features/login.feature` (this would write to main repo!)
+
+**2. Read the feature's scenario file and analyze for stable mode needs:**
 
 ```bash
 sqlite3 .jettypod/work.db "SELECT id, title, scenario_file FROM work_items WHERE id = <feature-id>"
 ```
 
-**2. Generate stable mode BDD scenarios** covering:
+**3. Generate stable mode BDD scenarios** covering:
 - **Error scenarios** - Invalid input, missing params, system errors, permission failures
 - **Edge cases** - Empty inputs, boundary values, special characters
 - **State consistency** - Concurrent ops, partial failures, invalid state transitions
 
-**3. Append scenarios to the feature file:**
+**4. Append scenarios to the feature file IN THE TEST WORKTREE:**
 
-```bash
-cat >> <scenario-file-path> << 'EOF'
+Use the Edit tool to append to `<worktree-path>/features/<feature-file>`:
 
+```gherkin
 # Stable Mode Scenarios - Error Handling and Edge Cases
 
 Scenario: [Error scenario title]
@@ -654,14 +674,15 @@ Scenario: [Edge case title]
   Given [context]
   When [edge case input]
   Then [expected behavior]
-EOF
 ```
 
-**4. Create step definitions** at `features/step_definitions/<feature-slug>-stable.steps.js`
+**5. Create step definitions IN THE TEST WORKTREE** at `<worktree-path>/features/step_definitions/<feature-slug>-stable.steps.js`
 
-**5. Commit BDD files immediately:**
+**6. Commit and merge the test worktree:**
 
 ```bash
+# Commit in the test worktree
+cd <worktree-path>
 git add features/
 git commit -m "test: Add stable mode BDD scenarios and step definitions
 
@@ -669,13 +690,12 @@ Added error handling and edge case scenarios for stable mode.
 - [N] new stable mode scenarios
 - Step definitions for validation and error handling"
 
-git push
+# Return to main repo and merge
+cd <main-repo-path>
+jettypod work merge <feature-id>
 ```
 
-**🛑 CRITICAL:** Commit IMMEDIATELY after generating files. Do NOT wait for user confirmation.
-Other assistants may be working in parallel - uncommitted files will block their merges.
-
-**6. Present proposal to user:**
+**7. Present proposal to user:**
 
 ```
 📋 Stable Mode Transition
@@ -826,6 +846,12 @@ jettypod work merge --release-lock     # Release held lock
 jettypod work start <chore-id>   # Create worktree and start chore
 ```
 
+**Create test worktree (for writing BDD scenarios):**
+```bash
+jettypod work tests <feature-id>  # Create worktree for writing tests
+jettypod work merge <feature-id>  # Merge tests back to main
+```
+
 **Set feature mode (BEFORE creating chores):**
 ```bash
 jettypod work set-mode <feature-id> stable

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

@@ -72,6 +72,14 @@ sqlite3 .jettypod/work.db "SELECT wi.id, wi.title, wi.status, wt.worktree_path,
 
 **🛑 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.
+
 **Example of valid output:**
 ```
 4|Add error handling|in_progress|/Users/erik/project/.jettypod-work/4-add-error-handling|feature/work-4-add-error-handling