@staff0rd/assist 0.707.1 → 0.708.1
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 +1 -1
- package/claude/commands/draft.md +2 -0
- package/claude/commands/refine.md +1 -0
- package/dist/commands/sessions/web/bundle.js +506 -506
- package/dist/index.js +110 -34
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -203,7 +203,7 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
|
|
|
203
203
|
- `assist backlog rewind <id> <phase> --reason <reason>` - Rewind an item to an earlier phase
|
|
204
204
|
- `assist backlog next [id] [--once]` - Pick and run the next backlog item, or open `/draft` if none remain
|
|
205
205
|
- `assist backlog refine [id] [--once] [--harness <claude|codex|pi>]` - Alias for `refine`
|
|
206
|
-
- `assist backlog run <id> [--harness <claude|codex|pi>] [--write|--no-write]` - Run a backlog item's plan phase-by-phase with the selected harness, defaulting to `harness.engine`; for Codex, write access uses the `workspace-write` sandbox and `--no-write` uses `read-only
|
|
206
|
+
- `assist backlog run <id> [--harness <claude|codex|pi>] [--write|--no-write]` - Run a backlog item's plan phase-by-phase with the selected harness, defaulting to `harness.engine`; for Codex, write access uses the `workspace-write` sandbox and `--no-write` uses `read-only`. Each phase prompt scopes the agent to the item's own repo: it must ask before modifying, committing or pushing any other repo
|
|
207
207
|
- `assist backlog export [file]` - Export every table in the backlog database to a file, or stdout
|
|
208
208
|
- `assist backlog import [file]` - Restore every table present in a dump back into the database (`-y, --yes` skips the prompt)
|
|
209
209
|
- `assist backlog associate-jira <id> [key]` - Associate a Jira ticket (bare key or browse URL); clears any GitHub issue on the item. `--clear` removes it
|
package/claude/commands/draft.md
CHANGED
|
@@ -79,6 +79,8 @@ Two tests for each phase before proposing the plan:
|
|
|
79
79
|
1. **Observable**: can you answer "does this work?" by running or inspecting the result? If a phase only produces internal plumbing with no observable effect, it's horizontal — restructure it.
|
|
80
80
|
2. **Self-contained**: would `assist verify` pass with only this phase's code committed — no unused exports, no dead stubs awaiting a later phase? If not, merge the producer and its consumer into the same phase.
|
|
81
81
|
|
|
82
|
+
**Every task stays in this repo.** An item belongs to the repo whose backlog it is in, and phase runs work only there. Never plan a task that edits, commits or pushes another repo (e.g. "In ~/git/other-repo, change..."). If the idea needs changes in another repo, leave that work out of the plan and tell the user to file it as a separate item in that repo's backlog.
|
|
83
|
+
|
|
82
84
|
Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
|
|
83
85
|
|
|
84
86
|
Most phases should NOT have manual checks. Only add `manualChecks` to a phase when the checks are genuinely difficult to automate (e.g. visual appearance, UX flow, hardware interaction). Do not add a final phase just for end-to-end verification — a `Review` phase is appended to every plan automatically, and authoring one is rejected.
|
|
@@ -79,6 +79,7 @@ When adding or restructuring plan phases, follow the same rules as /draft:
|
|
|
79
79
|
|
|
80
80
|
- **Vertical slices, not horizontal layers.** Each phase delivers a thin, working increment verifiable end-to-end — never "backend in phase 1, UI in phase 2".
|
|
81
81
|
- **Every phase must pass `assist verify` on its own.** Verification includes knip, which fails on unused exports — so every export a phase adds must have a caller wired up in that same phase. No "phase 2 will use it" scaffolding.
|
|
82
|
+
- **Every task stays in this repo.** Never add or keep a task that edits, commits or pushes another repo. If the user asks for one, leave it out of the plan and advise filing it as a separate item in that repo's backlog.
|
|
82
83
|
- If the user proposes a horizontal split, point out that the earlier phase won't verify (knip will flag the unused exports) and suggest a vertical restructure instead.
|
|
83
84
|
|
|
84
85
|
**To associate an external tracker** (Jira or GitHub — mutually exclusive, one per item; associating one clears the other):
|