jettypod 4.4.90 → 4.4.91

package/jettypod.js

@@ -245,16 +245,32 @@ Status: ${currentWork.status}
 <jettypod_essentials>
 JettyPod: Structured workflow system with skills that guide complex workflows.
 
-## ⚠️ CRITICAL: All Work Requires a Work Item
-**Claude CANNOT write code directly to main branch.**
-- All work requires: \`work create\` → \`work start\` → skill workflow → \`work merge\`
-- If user asks to implement something without a work item, create one first and invoke the matching skill
-- Pre-commit hooks block direct commits to main
+## ⚠️ CRITICAL: All Work Starts with request-routing
+
+**WHY:** request-routing creates a safe workspace (worktree) where your changes can actually be committed. Without it, you'll edit files on main, then discover the pre-commit hook blocks you—leaving uncommitted changes that can't be saved.
+
+**FIRST RESPONSE RULE:** If user describes ANY code change, your FIRST action must be invoking request-routing. Not after reading files. Not after understanding the problem. FIRST.
+
+**Trigger phrases → invoke request-routing immediately:**
+- "we should...", "let's...", "can you..." (implementation requests)
+- "fix", "broken", "not working", "bug" (bug reports)
+- "add", "build", "create", "implement" (feature requests)
+- "refactor", "migrate", "upgrade" (technical work)
+- "I noticed...", "I'm thinking..." (when followed by desired change)
+
+**⚠️ ANTI-PATTERN: Do NOT edit files before invoking request-routing.**
+Wrong: See problem → edit files → realize you're on main → ask about workflow
+Wrong: Read files → understand problem → try to fix → get blocked → create work item
+Right: User describes work → invoke request-routing → skill creates worktree → then edit
 
 ## ⚠️ CRITICAL: Skills are MANDATORY for workflows
 Skills auto-activate and MUST complete their full workflow:
-- epic-planning: Guides architectural decisions
-- feature-planning: Guides UX discovery + BDD scenarios
+- **request-routing**: ⚡ ENTRY POINT - routes ALL work requests to correct skill
+- epic-planning: Guides architectural decisions (invoked by request-routing)
+- feature-planning: Guides UX discovery + BDD scenarios (invoked by request-routing)
+- chore-planning: Guides technical work planning (invoked by request-routing)
+- bug-planning: Guides bug investigation (invoked by request-routing)
+- simple-improvement: Direct implementation for obvious changes (invoked by request-routing)
 - speed-mode: Implements happy path, THEN auto-invokes stable-mode
 - stable-mode: Adds error handling to speed implementation
 - external-transition: Guides launch preparation

package/package.json

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