jettypod 4.4.84 → 4.4.86

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jettypod",
3
- "version": "4.4.84",
3
+ "version": "4.4.86",
4
4
  "description": "AI-powered development workflow manager with TDD, BDD, and automatic test generation",
5
5
  "main": "jettypod.js",
6
6
  "bin": {
@@ -1,10 +1,22 @@
1
1
  ---
2
2
  name: plan-routing
3
- description: Route work requests to the appropriate planning skill. Use when user describes work they want to do - "build X", "fix Y", "add Z", "plan W". Analyzes intent and complexity to route to bug-planning, chore-planning, feature-planning, epic-planning, or simple-improvement. (project)
3
+ description: "⚡ ENTRY POINT FOR ALL WORK REQUESTS. Invoke this skill FIRST when user describes ANY work - 'build X', 'fix Y', 'add Z', 'create feature', 'implement'. Do NOT create work items or invoke other planning skills directly. This skill analyzes intent and routes to the correct workflow. (project)"
4
4
  ---
5
5
 
6
6
  # Plan Routing Skill
7
7
 
8
+ **⚡ UNIVERSAL ENTRY POINT** - This skill MUST be invoked FIRST when a user describes work they want done.
9
+
10
+ **DO NOT:**
11
+ - Create work items (`jettypod work create`) before invoking this skill
12
+ - Invoke feature-planning, bug-planning, chore-planning, epic-planning, or simple-improvement directly
13
+ - Ask the user what type of work this is
14
+
15
+ **DO:**
16
+ - Invoke this skill immediately when user describes work
17
+ - Let this skill analyze the request and route to the correct workflow
18
+ - The target skill will create work items as needed
19
+
8
20
  Routes user work requests to the correct planning workflow with minimal friction.
9
21
 
10
22
  ## Instructions
@@ -185,4 +197,3 @@ After stating your routing decision, immediately invoke the appropriate skill us
185
197
  - `simple-improvement`
186
198
 
187
199
  **This skill ends after invocation.** The target skill takes over.
188
- # Stable mode: Verified ambiguous request handling exists
@@ -9,9 +9,9 @@ description: Guide implementation of simple improvements to existing functionali
9
9
  ┌─────────────────────────────────────────────────────────────────────┐
10
10
  │ Simple Improvement Flow │
11
11
  │ │
12
- Feature Planning → [SIMPLE IMPROVEMENT] → Done
13
- ▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲
14
- YOU ARE HERE
12
+ Plan Routing → [SIMPLE IMPROVEMENT] → Done
13
+ ▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲▲
14
+ YOU ARE HERE
15
15
  │ │
16
16
  │ This is a LIGHTWEIGHT workflow - no speed/stable modes. │
17
17
  │ Single chore, direct implementation, done. │
@@ -22,7 +22,7 @@ Lightweight workflow for basic enhancements to existing functionality. Bypasses
22
22
 
23
23
  ## When to Use
24
24
 
25
- This skill is invoked by feature-planning when the user confirms their work is a **simple improvement**:
25
+ This skill is invoked by plan-routing when work is identified as a **simple improvement**:
26
26
  - Copy/text changes
27
27
  - Styling tweaks
28
28
  - Minor behavior adjustments
@@ -30,7 +30,7 @@ This skill is invoked by feature-planning when the user confirms their work is a
30
30
 
31
31
  ## When NOT to Use
32
32
 
33
- Route back to feature-planning for:
33
+ Route back to plan-routing for:
34
34
  - New functionality (even if small)
35
35
  - Changes requiring new data models
36
36
  - Complex logic changes
@@ -96,7 +96,7 @@ Scan the user's description for these patterns:
96
96
  | Multiple components | mentions 3+ different files/areas, "also need to" |
97
97
  | Architectural changes | "refactor", "restructure", "new system" |
98
98
 
99
- ❌ **Route back to feature-planning if ANY complexity signal detected:**
99
+ ❌ **Route back to plan-routing if ANY complexity signal detected:**
100
100
  - New database tables/columns needed
101
101
  - New API endpoints required
102
102
  - Complex conditional logic
@@ -114,11 +114,11 @@ Scan the user's description for these patterns:
114
114
  ```
115
115
  ⚠️ This change appears to require new data models or architectural changes. This is more than a simple improvement.
116
116
 
117
- I'm routing you back to feature-planning for proper planning with BDD scenarios.
117
+ I'm routing you back to plan-routing for proper planning.
118
118
  ```
119
119
 
120
120
  **Then IMMEDIATELY:**
121
- 1. Invoke feature-planning skill using the Skill tool
121
+ 1. Invoke plan-routing skill using the Skill tool
122
122
  2. END this skill (do not continue)
123
123
 
124
124
  **If confirmed simple:**