@pi-unipi/workflow 0.1.14 → 0.1.15

package/commands.ts

@@ -428,6 +428,9 @@ export function registerWorkflowCommands(
 
         if (ctx.hasUI) {
           ctx.ui.notify(`Running /${fullCommand}`, "info");
+          // Update extension status with active command name
+          const ralphStatus = options.isRalphDetected() ? "✓ rl" : "○ rl";
+          ctx.ui.setStatus("unipi-workflow", `⚡ wf:${cmd.name} ${ralphStatus}`);
         }
       },
     });

package/index.ts

@@ -143,8 +143,8 @@ export default function (pi: ExtensionAPI) {
 
     // Show workflow status in UI
     if (ctx.hasUI) {
-      const ralphStatus = ralphDetected ? "✓ ralph" : "○ ralph";
-      ctx.ui.setStatus("unipi-workflow", `⚡ workflow ${ralphStatus}`);
+      const ralphStatus = ralphDetected ? "✓ rl" : "○ rl";
+      ctx.ui.setStatus("unipi-workflow", `⚡ wf ${ralphStatus}`);
     }
   });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pi-unipi/workflow",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "Structured development workflow commands for Pi coding agent",
   "type": "module",
   "license": "MIT",

package/skills/gather-context/SKILL.md

@@ -102,7 +102,30 @@ Organize findings into clear categories:
 
 ### Phase 4: Present & Handoff
 
-Present findings to user. Then:
+Present findings to user.
+
+#### Save Gate
+
+If the user already specified whether to save (e.g., "save findings to memory" or "just show me"), skip this gate and follow their preference. Otherwise, ask:
+
+```
+ask_user({
+  question: "Save this context?",
+  context: "Context gathered from {N} files across {areas}. Summary includes structure, patterns, prior art, and recommendations.",
+  options: [
+    { label: "Save to memory", description: "Store findings in .unipi/memory/ for future sessions", value: "save" },
+    { label: "Save to file", description: "Write findings to .unipi/docs/research/<topic>.md", value: "file" },
+    { label: "Don't save", description: "Discard — context was just for this session", value: "discard" }
+  ],
+  allowFreeform: false
+})
+```
+
+- **Save to memory:** Write findings to `.unipi/memory/` following the consolidate skill's memory file format.
+- **Save to file:** Write findings to `.unipi/docs/research/<topic>.md` using the synthesis output format from Phase 3.
+- **Don't save:** Skip — findings stay in conversation only.
+
+After the save decision, hand off:
 
 > "Context gathered. Ready to brainstorm solutions?"
 ```
@@ -119,4 +142,4 @@ The brainstorm will start with this context already available — no need to re-
 - Subagent support enables parallel research when available
 - Findings feed directly into brainstorm — natural workflow
 - Can be run standalone for exploration, or as pre-brainstorm step
-- Output is ephemeral (in conversation) unless user requests saving
+- Output is ephemeral (in conversation) unless user requests saving — save gate at end of Phase 4 offers explicit save-to-memory or save-to-file

package/skills/review-work/SKILL.md

@@ -37,6 +37,14 @@ Review what was built, verify task completion, run codebase checks, add reviewer
 
 **Exit:** On correct branch. Plan loaded.
 
+### Ralph Status Check
+
+If a ralph loop was used for this work (check `.unipi/ralph/` for a matching state file):
+1. Read `.unipi/ralph/{name}.state.json` — note iteration count, reflection findings
+2. Read `.unipi/ralph/{name}.md` — check checklist completion
+3. Note any items marked incomplete or abandoned across iterations
+4. Include this loop context in your reviewer remarks
+
 ---
 
 ## Phase 2: Check Task Completion

package/skills/work/SKILL.md

@@ -71,6 +71,22 @@ Load plan, review critically, execute tasks, commit when complete.
 
 **Exit:** Plan reviewed, ready to execute.
 
+### Ralph Loop Decision
+
+Count the non-completed tasks (`unstarted:`, `in-progress:`, `failed:`). If you have the `ralph_start` tool available and 3+ non-trivial tasks remain, consider a ralph loop for resilience:
+
+```
+ralph_start({
+  name: "{plan-topic}",
+  taskContent: "# {Plan Title}\n\n{overview}\n\n## Goals\n- {goal1}\n- {goal2}\n\n## Checklist\n- [ ] {task1}\n- [ ] {task2}\n- [ ] {task3}",
+  maxIterations: 50,
+  itemsPerIteration: 2,
+  reflectEvery: 5
+})
+```
+
+**To skip:** Just proceed to Phase 3 and execute tasks directly. Ralph is a helper, not a requirement.
+
 ---
 
 ## Phase 3: Execute Tasks
@@ -142,7 +158,8 @@ When all tasks are `completed:`:
 
 1. Run final verification (tests, lint, build)
 2. Commit all remaining changes
-3. Inform user based on branch strategy:
+3. If using a ralph loop, emit `COMPLETE` and call `ralph_done` to cleanly exit
+4. Inform user based on branch strategy:
 
 **If working in worktree:**
 > "All tasks complete. Worktree: `{branch}`. Recommend reviewing before merge."