jettypod 4.4.85 → 4.4.87

package/apps/dashboard/components/KanbanBoard.tsx

@@ -105,6 +105,11 @@ function KanbanCard({ item, epicTitle, showEpic = false, isInFlight = false, onT
   const hasChores = allChores.length > 0;
   const hasIncompleteChores = incompleteChores.length > 0;
 
+  // Calculate bugs for expandable section
+  const allBugs = item.bugs || [];
+  const incompleteBugs = allBugs.filter(b => b.status !== 'done');
+  const hasBugs = allBugs.length > 0;
+
   const handleCardClick = () => {
     router.push(`/work/${item.id}`);
   };
@@ -186,24 +191,40 @@ function KanbanCard({ item, epicTitle, showEpic = false, isInFlight = false, onT
           )}
         </div>
       </div>
-      {/* Show expandable chores section for features with chores */}
-      {hasChores && (
+      {/* Show expandable section for features with chores or bugs */}
+      {(hasChores || hasBugs) && (
         <div className={`border-t ${isDone ? 'border-green-200 dark:border-green-800' : 'border-zinc-200 dark:border-zinc-700'}`}>
           <button
             onClick={() => setExpanded(!expanded)}
-            className={`w-full px-3 py-1.5 flex items-center gap-1.5 text-xs transition-colors ${
+            className={`w-full px-3 py-1.5 flex items-start gap-1.5 text-xs transition-colors ${
               isDone
                 ? 'text-green-700 dark:text-green-400 hover:bg-green-100 dark:hover:bg-green-900/30'
                 : 'text-zinc-600 dark:text-zinc-300 hover:bg-zinc-50 dark:hover:bg-zinc-700/50'
             }`}
           >
-            <span>{expanded ? '▼' : '▶'}</span>
-            <span>🔧</span>
-            <span>
-              {isDone
-                ? `${allChores.length === 0 ? 'no' : allChores.length} chore${allChores.length !== 1 ? 's' : ''}`
-                : `${incompleteChores.length === 0 ? 'no' : incompleteChores.length}${item.mode ? ` ${item.mode} mode` : ''} chore${incompleteChores.length !== 1 ? 's' : ''} left`}
-            </span>
+            <span className="mt-0.5">{expanded ? '▼' : '▶'}</span>
+            <div className="flex flex-col gap-0.5">
+              {hasChores && (
+                <div className="flex items-center gap-1.5">
+                  <span>🔧</span>
+                  <span>
+                    {isDone
+                      ? `${allChores.length === 0 ? 'no' : allChores.length} chore${allChores.length !== 1 ? 's' : ''}`
+                      : `${incompleteChores.length === 0 ? 'no' : incompleteChores.length}${item.mode ? ` ${item.mode} mode` : ''} chore${incompleteChores.length !== 1 ? 's' : ''} left`}
+                  </span>
+                </div>
+              )}
+              {hasBugs && (
+                <div className="flex items-center gap-1.5">
+                  <span>🐛</span>
+                  <span>
+                    {isDone
+                      ? `${allBugs.length === 0 ? 'no' : allBugs.length} bug${allBugs.length !== 1 ? 's' : ''}`
+                      : `${incompleteBugs.length === 0 ? 'no' : incompleteBugs.length} bug${incompleteBugs.length !== 1 ? 's' : ''} left`}
+                  </span>
+                </div>
+              )}
+            </div>
           </button>
           {expanded && (
             <div className="px-3 pb-2 space-y-1">
@@ -237,6 +258,32 @@ function KanbanCard({ item, epicTitle, showEpic = false, isInFlight = false, onT
                   </Link>
                 );
               })}
+              {allBugs.map((bug) => {
+                const isComplete = bug.status === 'done';
+                return (
+                  <Link
+                    key={bug.id}
+                    href={`/work/${bug.id}`}
+                    className={`block py-1 px-2 text-xs rounded transition-colors ${
+                      isComplete
+                        ? 'bg-green-100 dark:bg-green-900/30 border border-green-200 dark:border-green-800/50'
+                        : 'hover:bg-zinc-100 dark:hover:bg-zinc-700'
+                    }`}
+                  >
+                    <div className="flex items-center gap-2">
+                      <span className={`font-mono ${isComplete ? 'text-zinc-500' : 'text-zinc-400'}`}>#{bug.id}</span>
+                      <span>🐛</span>
+                      <span className={`truncate ${
+                        isComplete
+                          ? 'text-zinc-500'
+                          : 'text-zinc-700 dark:text-zinc-300'
+                      }`}>
+                        {bug.title || <span className="text-zinc-400 italic">(Untitled)</span>}
+                      </span>
+                    </div>
+                  </Link>
+                );
+              })}
             </div>
           )}
         </div>

package/apps/dashboard/lib/db.ts

@@ -23,6 +23,7 @@ export interface WorkItem {
   display_order: number | null;
   children?: WorkItem[];
   chores?: WorkItem[];
+  bugs?: WorkItem[];
   current_step?: number | null;
   total_steps?: number | null;
 }
@@ -279,6 +280,26 @@ export function getKanbanData(doneLimit: number = 50): KanbanData {
       }
     }
 
+    // Get all bugs that belong to features (for bug expansion)
+    const featureBugs = db.prepare(`
+      SELECT b.id, b.type, b.title, b.description, b.status, b.parent_id, b.epic_id,
+             b.branch_name, b.mode, b.phase, b.completed_at, b.created_at
+      FROM work_items b
+      INNER JOIN work_items f ON b.parent_id = f.id
+      WHERE b.type = 'bug' AND f.type = 'feature'
+      ORDER BY b.id
+    `).all() as WorkItem[];
+
+    // Group bugs by parent feature ID
+    const bugsByFeature = new Map<number, WorkItem[]>();
+    for (const bug of featureBugs) {
+      if (bug.parent_id) {
+        const existing = bugsByFeature.get(bug.parent_id) || [];
+        existing.push(bug);
+        bugsByFeature.set(bug.parent_id, existing);
+      }
+    }
+
     // Get kanban-eligible items:
     // - Features (type = 'feature')
     // - Chores that are NOT children of features (parent is null, or parent is an epic)
@@ -319,9 +340,10 @@ export function getKanbanData(doneLimit: number = 50): KanbanData {
       // Strip parent_type from the item
       const { parent_type, ...cleanItem } = item;
 
-      // Attach chores to features
+      // Attach chores and bugs to features
       if (cleanItem.type === 'feature') {
         cleanItem.chores = choresByFeature.get(cleanItem.id) || [];
+        cleanItem.bugs = bugsByFeature.get(cleanItem.id) || [];
       }
 
       if (cleanItem.status === 'in_progress') {

package/package.json

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

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

@@ -1,6 +1,6 @@
 ---
 name: bug-planning
-description: Guide structured bug investigation with symptom capture, hypothesis testing, and root cause identification. Invoked by plan-routing when user reports a bug, mentions unexpected behavior, or describes something broken. (project)
+description: Guide structured bug investigation with symptom capture, hypothesis testing, and root cause identification. Invoked by request-routing when user reports a bug, mentions unexpected behavior, or describes something broken. (project)
 ---
 
 # Bug Planning Skill

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

@@ -1,6 +1,6 @@
 ---
 name: chore-planning
-description: Guide standalone chore planning with automatic type classification and routing to chore-mode. Invoked by plan-routing for substantial technical work - refactoring, infrastructure, migrations, or enhancements where the implementation approach is obvious. (project)
+description: Guide standalone chore planning with automatic type classification and routing to chore-mode. Invoked by request-routing for substantial technical work - refactoring, infrastructure, migrations, or enhancements where the implementation approach is obvious. (project)
 ---
 
 # Chore Planning Skill

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

@@ -1,6 +1,6 @@
 ---
 name: epic-planning
-description: Guide epic planning with feature brainstorming and optional architectural decision prototyping. Invoked by plan-routing for large multi-feature initiatives that need to be broken down into features. (project)
+description: Guide epic planning with feature brainstorming and optional architectural decision prototyping. Invoked by request-routing for large multi-feature initiatives that need to be broken down into features. (project)
 ---
 
 # Epic Planning Skill

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

@@ -1,6 +1,6 @@
 ---
 name: feature-planning
-description: Guide feature planning with UX approach exploration and BDD scenario generation. Invoked by plan-routing when implementing NEW user-facing behavior that requires UX decisions (multiple valid approaches to explore). (project)
+description: Guide feature planning with UX approach exploration and BDD scenario generation. Invoked by request-routing when implementing NEW user-facing behavior that requires UX decisions (multiple valid approaches to explore). (project)
 ---
 
 # Feature Planning Skill

package/skills-templates/{plan-routing → request-routing}/SKILL.md

@@ -1,9 +1,21 @@
 ---
-name: plan-routing
-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)
+name: request-routing
+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)"
 ---
 
-# Plan Routing Skill
+# Request Routing Skill
+
+**⚡ UNIVERSAL ENTRY POINT** - This skill MUST be invoked FIRST when a user describes work they want done.
+
+**DO NOT:**
+- Create work items (`jettypod work create`) before invoking this skill
+- Invoke feature-planning, bug-planning, chore-planning, epic-planning, or simple-improvement directly
+- Ask the user what type of work this is
+
+**DO:**
+- Invoke this skill immediately when user describes work
+- Let this skill analyze the request and route to the correct workflow
+- The target skill will create work items as needed
 
 Routes user work requests to the correct planning workflow with minimal friction.
 
@@ -185,4 +197,3 @@ After stating your routing decision, immediately invoke the appropriate skill us
 - `simple-improvement`
 
 **This skill ends after invocation.** The target skill takes over.
-# Stable mode: Verified ambiguous request handling exists

package/skills-templates/simple-improvement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: simple-improvement
-description: Guide implementation of simple improvements to existing functionality. Invoked by plan-routing for straightforward changes like copy changes, styling tweaks, or minor behavior adjustments where the implementation is obvious. (project)
+description: Guide implementation of simple improvements to existing functionality. Invoked by request-routing for straightforward changes like copy changes, styling tweaks, or minor behavior adjustments where the implementation is obvious. (project)
 ---
 
 # Simple Improvement Skill
@@ -22,7 +22,7 @@ Lightweight workflow for basic enhancements to existing functionality. Bypasses
 
 ## When to Use
 
-This skill is invoked by plan-routing when work is identified as a **simple improvement**:
+This skill is invoked by request-routing when work is identified as a **simple improvement**:
 - Copy/text changes
 - Styling tweaks
 - Minor behavior adjustments
@@ -30,7 +30,7 @@ This skill is invoked by plan-routing when work is identified as a **simple impr
 
 ## When NOT to Use
 
-Route back to plan-routing for:
+Route back to request-routing for:
 - New functionality (even if small)
 - Changes requiring new data models
 - Complex logic changes
@@ -96,7 +96,7 @@ Scan the user's description for these patterns:
 | Multiple components | mentions 3+ different files/areas, "also need to" |
 | Architectural changes | "refactor", "restructure", "new system" |
 
-❌ **Route back to plan-routing if ANY complexity signal detected:**
+❌ **Route back to request-routing if ANY complexity signal detected:**
 - New database tables/columns needed
 - New API endpoints required
 - Complex conditional logic
@@ -114,11 +114,11 @@ Scan the user's description for these patterns:
 ```
 ⚠️ This change appears to require new data models or architectural changes. This is more than a simple improvement.
 
-I'm routing you back to plan-routing for proper planning.
+I'm routing you back to request-routing for proper planning.
 ```
 
 **Then IMMEDIATELY:**
-1. Invoke plan-routing skill using the Skill tool
+1. Invoke request-routing skill using the Skill tool
 2. END this skill (do not continue)
 
 **If confirmed simple:**