@staff0rd/assist 0.136.2 → 0.138.0

package/README.md

@@ -37,7 +37,6 @@ After installation, the `assist` command will be available globally. You can als
 - `/commit` - Commit only relevant files from the session
 - `/devlog` - Generate devlog entry for the next unversioned day
 - `/draft` - Draft a new backlog item with LLM-assisted questioning
-- `/next-backlog-item` - Pick and implement the next backlog item
 - `/pr` - Raise a PR with a concise description
 - `/refactor` - Run refactoring checks for code quality
 - `/restructure` - Analyze and restructure tightly-coupled files
@@ -105,6 +104,7 @@ After installation, the `assist` command will be available globally. You can als
 - `assist refactor ignore <file>` - Add a file to the refactor ignore list
 - `assist refactor rename file <source> <destination>` - Rename/move a TypeScript file and update all imports (dry-run by default, use `--apply` to execute)
 - `assist refactor rename symbol <file> <oldName> <newName>` - Rename a variable, function, class, or type across the project (dry-run by default, use `--apply` to execute)
+- `assist refactor extract <file> <functionName> <destination>` - Extract a function and its private dependencies to a new file (dry-run by default, use `--apply` to execute)
 - `assist refactor restructure [pattern]` - Analyze import graph and restructure tightly-coupled files into nested directories
 - `assist devlog list` - Group git commits by date
 - `assist devlog next` - Show commits for the day after the last versioned entry

package/claude/commands/draft.md

@@ -34,10 +34,12 @@ Once you have enough context, propose a complete backlog item. Show it to the us
 
 **Plan:**
 - Phase 1: (name) — tasks...
-- Phase 2: (name) — tasks...
+- Phase 2: (name) — tasks... [manual checks: ...]
 
 Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
 
+Most phases should NOT have manual checks — prefer automated verification via the `verify` field on tasks. Only add `manualChecks` to a phase when the checks are genuinely difficult to automate (e.g. visual appearance, UX flow, hardware interaction). The last phase should always have at least one manual check to confirm the feature works end-to-end.
+
 ## Step 4: Iterate
 
 Ask the user if they want to change anything. Iterate until they confirm.
@@ -57,7 +59,8 @@ Once confirmed, pipe the JSON to the CLI. The JSON must match this shape:
       "name": "Phase name",
       "tasks": [
         { "task": "Do something", "verify": "optional verification step" }
-      ]
+      ],
+      "manualChecks": ["optional — only for checks that can't be automated"]
     }
   ]
 }

package/claude/settings.json

@@ -51,8 +51,7 @@
 			"Bash(assist seq auth list:*)",
 			"Bash(assist screenshot:*)",
 			"Bash(assist roam show-claude-code-icon:*)",
-			"SlashCommand(/next-backlog-item)",
-			"SlashCommand(/verify)",
+"SlashCommand(/verify)",
 			"SlashCommand(/commit)",
 			"SlashCommand(/devlog)",
 			"SlashCommand(/refactor)",
@@ -66,8 +65,7 @@
 			"SlashCommand(/voice-logs)",
 			"SlashCommand(/journal)",
 			"SlashCommand(/standup)",
-			"Skill(next-backlog-item)",
-			"Skill(verify)",
+"Skill(verify)",
 			"Skill(commit)",
 			"Skill(devlog)",
 			"Skill(refactor)",

package/dist/index.js

@@ -6,7 +6,7 @@ import { Command } from "commander";
 // package.json
 var package_default = {
   name: "@staff0rd/assist",
-  version: "0.136.2",
+  version: "0.138.0",
   type: "module",
   main: "dist/index.js",
   bin: {
@@ -2290,7 +2290,8 @@ var planTaskSchema = z2.strictObject({
 });
 var planPhaseSchema = z2.strictObject({
   name: z2.string(),
-  tasks: z2.array(planTaskSchema)
+  tasks: z2.array(planTaskSchema),
+  manualChecks: z2.array(z2.string()).optional()
 });
 var backlogItemSchema = z2.strictObject({
   id: z2.number(),
@@ -2611,12 +2612,34 @@ import chalk35 from "chalk";
 import chalk34 from "chalk";
 
 // src/commands/backlog/buildPhasePrompt.ts
-function buildPhasePrompt(item, phaseIndex, phase) {
-  const tasks = phase.tasks.map((t) => {
+function formatTasks(phase) {
+  return phase.tasks.map((t) => {
     let line = `- ${t.task}`;
     if (t.verify) line += ` (verify: ${t.verify})`;
     return line;
   }).join("\n");
+}
+function buildManualCheckLines(manualChecks, isLastPhase) {
+  if (manualChecks.length > 0) {
+    return [
+      "",
+      "Before marking this phase as done, ask the user to perform these manual checks:",
+      ...manualChecks.map((c) => `- ${c}`),
+      "",
+      "Wait for the user to confirm all manual checks pass before proceeding."
+    ];
+  }
+  if (isLastPhase) {
+    return [
+      "",
+      "This is the final phase. Before marking it as done, ask the user to manually verify",
+      "that the feature works end-to-end and all acceptance criteria are met.",
+      "Wait for the user to confirm before proceeding."
+    ];
+  }
+  return [];
+}
+function buildContextLines(item, phaseIndex, phase) {
   const ac = item.acceptanceCriteria.map((c) => `- ${c}`).join("\n");
   return [
     `You are implementing phase ${phaseIndex + 1} of backlog item #${item.id}: ${item.name}`,
@@ -2628,11 +2651,22 @@ function buildPhasePrompt(item, phaseIndex, phase) {
     "",
     `Phase ${phaseIndex + 1}: ${phase.name}`,
     "Tasks:",
-    tasks,
+    formatTasks(phase)
+  ];
+}
+function buildPhasePrompt(item, phaseIndex, phase, totalPhases) {
+  const isLastPhase = phaseIndex === totalPhases - 1;
+  const manualChecks = phase.manualChecks ?? [];
+  const needsConfirmation = manualChecks.length > 0 || isLastPhase;
+  const confirmSuffix = needsConfirmation ? " and the user confirms" : "";
+  return [
+    ...buildContextLines(item, phaseIndex, phase),
     "",
     "Focus ONLY on this phase. Do not work on other phases.",
     "When you have completed all tasks for this phase, run /verify to check your work.",
-    `Once verify passes, run: assist backlog phase-done ${item.id} ${phaseIndex}`
+    ...buildManualCheckLines(manualChecks, isLastPhase),
+    "",
+    `Once verify passes${confirmSuffix}, run: assist backlog phase-done ${item.id} ${phaseIndex}`
   ].filter((line) => line !== void 0).join("\n");
 }
 
@@ -2757,7 +2791,7 @@ async function executePhase(item, phaseIndex, phases) {
     )
   );
   const { child, done: done2 } = spawnClaude(
-    buildPhasePrompt(item, phaseIndex, phase)
+    buildPhasePrompt(item, phaseIndex, phase, phases.length)
   );
   watchForMarker(child);
   await done2;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@staff0rd/assist",
-	"version": "0.136.2",
+	"version": "0.138.0",
 	"type": "module",
 	"main": "dist/index.js",
 	"bin": {

package/claude/commands/next-backlog-item.md

@@ -1,17 +0,0 @@
----
-description: Pick and implement the next backlog item
----
-
-Run `assist backlog list --status todo --verbose 2>&1` to see all available backlog items.
-
-Choose ONE item to implement. You may pick whichever item you like. Read the item's name, description, and acceptance criteria carefully. If anything is unclear or ambiguous, ask the user for clarification before proceeding.
-
-Once you have chosen an item, run `assist backlog start <id>` to mark it as in-progress.
-
-Implement the item fully, satisfying ALL acceptance criteria. Do not skip any.
-
-When implementation is complete, run `/verify` and fix any issues until it passes.
-
-Then stop and wait for the user. Do NOT call `assist backlog done` yet. Inform the user the item is ready and wait for them to call `/commit`.
-
-Only after the user has called `/commit` and the commit succeeds, run `assist backlog done <id>` to mark the item as done.