@brainervirus/workit-claude-code 7.4.0 → 7.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-claude-code",
-  "version": "7.4.0",
+  "version": "7.5.0",
   "private": false,
   "description": "Workit Claude Code plugin — session and per-turn task context, branch policy on git shell commands, workit method skills, and verifier/reviewer/implementer agents",
   "keywords": [
@@ -39,8 +39,8 @@
     "build": "bun scripts/build.ts"
   },
   "devDependencies": {
-    "@brainervirus/workit-cli": "^7.4.0",
-    "@brainervirus/workit-core": "^7.4.0"
+    "@brainervirus/workit-cli": "^7.5.0",
+    "@brainervirus/workit-core": "^7.5.0"
   },
   "engines": {
     "node": ">=24"

package/skills/fanout/SKILL.md

@@ -14,30 +14,30 @@ ceremony; do it yourself.
    per slice an id, branch, TIER, the file-scope manifest (SCOPE globs),
    `owns` for shared files (lockfile, registry, barrels), `dependsOn` only for
    a real dependency (independent PRs off trunk are the default), and the
-   brief fields. `workit fanout plan <plan.json>` refuses an empty brief field
-   (exit 2) and two slices that may write one file (exit 3) with a fix: an
-   owner for a shared file, or a dependency that serializes them. Apply it and
-   re-run: refuse to spawn while a field is empty or the plan is refused.
-   Its `waves` say which slices may run together; keep 4-6 in flight.
+   brief fields. `workit fanout plan <plan.json>` refuses an empty or
+   placeholder (`<goal>`, `TBD`) brief field (exit 2) and two slices that may
+   write one file (exit 3) with a fix: an owner for a shared file, or a
+   dependency that serializes them. Apply it and re-run: refuse to spawn while
+   a field is empty or the plan is refused. Its `waves` say which slices may
+   run together; keep 4-6 in flight.
 2. **Brief each worker** from its slice with the fixed template: GOAL, SCOPE,
    CONTEXT (pointers, not pasted text), ACCEPTANCE (Given/When/Then), VERIFY
-   (exact commands), TIER, TIMEBOX, FORBIDDEN, REPORT, STANDING. STANDING is
-   every standing order and user directive so far, pasted verbatim into each
-   spawn and respawn, because directives decay across resumes.
+   (exact commands), TIER, TIMEBOX, SCRATCH, FORBIDDEN, REPORT, STANDING.
+   STANDING is every standing order and user directive so far, pasted
+   verbatim into each spawn and respawn: directives decay across resumes.
 3. **Spawn all workers in one message**, in the background, each in its own
-   worktree (Claude Code: the `implementer` agent; elsewhere
-   `git worktree add --detach ../<repo>-wt/<slug> origin/<base>`). The first
-   command a worker runs is `workit git branch <branch> --base <base>`.
-4. **Judge liveness by side effects only:** new commits and pushes
-   (`git log <branch>`), PR and check changes (`workit pr status --branch <b>`).
-   No progress past the timebox means stuck. Stop the old worker and observe
-   that it exited (a timeout is not proof). `git worktree remove --force`
-   drops its uncommitted changes, so first record `git -C <wt> status --short`
-   in the ledger or your report; only then remove the worktree. Respawn with
-   the brief in `MODE: resume` (original, later directives, its last report):
-   the new worker runs `git switch <branch>` in its fresh worktree instead of
-   `workit git branch`. Never two live workers on one branch. Replace at most
-   twice, then re-slice or report the gap. Never chain resumes.
+   worktree: Claude Code's `implementer` agent (first command `workit git
+   branch <branch> --base <base>`); elsewhere `workit fanout worktree create
+   <slice>`, which prints the SCRATCH dir. Refill from `fanout status`.
+4. **Judge liveness by side effects only:** `workit fanout status` (head age,
+   PR, CI, verdict, landed; STUCK past the TIMEBOX, default 30 min). Stop a
+   stuck worker and observe that it exited (a timeout is not proof). Removing
+   a worktree drops its uncommitted changes: `workit fanout worktree release
+   <slice>` records `git status` in the ledger first and refuses them without
+   `--force` (native worktrees: record `git -C <wt> status --short` first).
+   Respawn in `MODE: resume` (brief, directives, last report), same branch.
+   Never two live workers on one branch. Replace at most twice, then re-slice
+   or report the gap. Never chain resumes.
 5. **Verify each slice independently.** A fresh agent that did not write it
    (Claude Code: the `verifier` agent) runs VERIFY and verify-<app>, then
    `workit ledger verdict <result> --branch <b> --how "<evidence>"` under the
@@ -47,12 +47,12 @@ ceremony; do it yourself.
 6. **Fan in** with `workit fanout check`: out-of-scope files (any file outside
    it stops the fan-in), and `git merge-tree` conflicts with trunk and between
    siblings, charged to the slice that lands later. Fix what it names (an
-   out-of-scope edit becomes a follow-up slice) until it exits 0. A landed
-   slice reads as not found: re-plan without it and drop it from dependents'
-   `dependsOn`. Then `workit ledger check --branch <b>` per slice; land in its
-   order. Stacked slices: `workit stack plan <bottom> … <top>` once, then
-   `workit stack sync` and `land`. Only you touch topology: workers never
-   rebase, retarget or merge. Then workit-ship.
+   out-of-scope edit becomes a follow-up slice) until it exits 0. A slice
+   whose PR merged reads as landed; its dependents stop waiting. Then
+   `workit ledger check --branch <b>` per slice, land in `fanout status` order
+   and release the worktrees you made. Stacks: `workit stack plan <bottom> …
+   <top>` once, then `stack sync` and `land`. Only you touch topology: workers
+   never rebase, retarget or merge. Then workit-ship.
 
 ## Example
 

package/skills/fanout/references/brief.md

@@ -14,6 +14,7 @@ ACCEPTANCE:
 VERIFY: <exact commands, e.g. `workit check test`, the verify-<app> feature to drive>
 TIER: <mundane | standard | hard: how much model the slice needs>
 TIMEBOX: <wall clock or turn budget; past it without a new commit you will be replaced>
+SCRATCH: <your own temp dir: the one `fanout worktree create` printed, else `mktemp -d`; never a shared path>
 FORBIDDEN: <no edits outside SCOPE; no rebase, retarget, merge or force-push; no new dependencies; ...>
 REPORT: branch, head SHA, files changed, each VERIFY command with its exit code,
   each ACCEPTANCE line met / not met, rulings you made (`workit ledger ruling`),
@@ -37,6 +38,7 @@ ACCEPTANCE:
 VERIFY: `workit check test`; verify-api feature "usage"
 TIER: standard
 TIMEBOX: 45 minutes
+SCRATCH: ../app-wt/usage-endpoint/.workit-scratch
 FORBIDDEN: no edits outside SCOPE; no schema migration; no rebase or force-push; no new packages
 REPORT: as in the template
 STANDING: conventional commits; no comments that restate code; ask nothing, record rulings instead
@@ -50,7 +52,9 @@ verify, forbidden must be filled; tier is mundane, standard or hard). `base`
 defaults to the trunk, or to the branch of a single `dependsOn` slice (a
 stack); `worktree` defaults to `../<repo>-wt/<id>`. `owns` claims a shared
 file another slice's glob also matches. Globs that match no file yet are compared
-through a sample path. Escape literal brackets: `"app/\\[id\\]/page.tsx"`.
+through a sample path. Use `/` as the separator; a backslash only escapes
+literal brackets: `"app/\\[id\\]/page.tsx"`. A `timebox` such as `45 minutes`
+is the slice's STUCK threshold in `workit fanout status`.
 
 ```json
 {