@staff0rd/assist 0.136.1 → 0.137.0

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/README.md CHANGED
@@ -37,7 +37,6 @@ After installation, the `assist` command will be available globally. You can als
37
37
  - `/commit` - Commit only relevant files from the session
38
38
  - `/devlog` - Generate devlog entry for the next unversioned day
39
39
  - `/draft` - Draft a new backlog item with LLM-assisted questioning
40
- - `/next-backlog-item` - Pick and implement the next backlog item
41
40
  - `/pr` - Raise a PR with a concise description
42
41
  - `/refactor` - Run refactoring checks for code quality
43
42
  - `/restructure` - Analyze and restructure tightly-coupled files
@@ -105,6 +104,7 @@ After installation, the `assist` command will be available globally. You can als
105
104
  - `assist refactor ignore <file>` - Add a file to the refactor ignore list
106
105
  - `assist refactor rename file <source> <destination>` - Rename/move a TypeScript file and update all imports (dry-run by default, use `--apply` to execute)
107
106
  - `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)
107
+ - `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)
108
108
  - `assist refactor restructure [pattern]` - Analyze import graph and restructure tightly-coupled files into nested directories
109
109
  - `assist devlog list` - Group git commits by date
110
110
  - `assist devlog next` - Show commits for the day after the last versioned entry
@@ -34,10 +34,12 @@ Once you have enough context, propose a complete backlog item. Show it to the us
34
34
 
35
35
  **Plan:**
36
36
  - Phase 1: (name) — tasks...
37
- - Phase 2: (name) — tasks...
37
+ - Phase 2: (name) — tasks... [manual checks: ...]
38
38
 
39
39
  Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
40
40
 
41
+ 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.
42
+
41
43
  ## Step 4: Iterate
42
44
 
43
45
  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:
57
59
  "name": "Phase name",
58
60
  "tasks": [
59
61
  { "task": "Do something", "verify": "optional verification step" }
60
- ]
62
+ ],
63
+ "manualChecks": ["optional — only for checks that can't be automated"]
61
64
  }
62
65
  ]
63
66
  }
@@ -51,8 +51,7 @@
51
51
  "Bash(assist seq auth list:*)",
52
52
  "Bash(assist screenshot:*)",
53
53
  "Bash(assist roam show-claude-code-icon:*)",
54
- "SlashCommand(/next-backlog-item)",
55
- "SlashCommand(/verify)",
54
+ "SlashCommand(/verify)",
56
55
  "SlashCommand(/commit)",
57
56
  "SlashCommand(/devlog)",
58
57
  "SlashCommand(/refactor)",
@@ -66,8 +65,7 @@
66
65
  "SlashCommand(/voice-logs)",
67
66
  "SlashCommand(/journal)",
68
67
  "SlashCommand(/standup)",
69
- "Skill(next-backlog-item)",
70
- "Skill(verify)",
68
+ "Skill(verify)",
71
69
  "Skill(commit)",
72
70
  "Skill(devlog)",
73
71
  "Skill(refactor)",