@brainervirus/workit-claude-code 7.2.0 → 7.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-claude-code",
-  "version": "7.2.0",
+  "version": "7.3.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.2.0",
-    "@brainervirus/workit-core": "^7.2.0"
+    "@brainervirus/workit-cli": "^7.3.0",
+    "@brainervirus/workit-core": "^7.3.0"
   },
   "engines": {
     "node": ">=24"

package/skills/fanout/SKILL.md

@@ -10,41 +10,49 @@ verifiable alone. Code-coupled work stays with one owner, who fans out after
 the blocking part lands. A worker whose whole job is re-running one command is
 ceremony; do it yourself.
 
-1. **Slice** (workit-shape): each slice gets a branch, a file-scope manifest
-   (the globs it may write) and, if it depends on another, its stack parent.
-2. **Check disjointness.** No two manifests overlap. Shared files (lockfile,
-   registry, barrel exports) belong to one slice, or to you after fan-in.
-3. **Brief each worker** with the fixed template and refuse to spawn while a
-   field is empty: GOAL, SCOPE (the manifest), CONTEXT (pointers, not pasted
-   text), ACCEPTANCE (Given/When/Then), VERIFY (exact commands), 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. Template: `references/brief.md`.
-4. **Spawn all workers in one message**, in the background, each in its own
+1. **Plan the slices** (workit-shape) in a plan file (`references/brief.md`):
+   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.
+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.
+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>`.
-5. **Judge liveness by side effects only:** new commits and pushes
+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` (consolidated: original, later directives, its last report):
+   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.
-6. **Verify each slice independently.** A fresh agent that did not write it
+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
    session you started it with (`WORKIT_SESSION_ID=<lead>-v<n>`, set by you,
    never chosen by the author; Claude Code: the hook names one).
    A worker's report is a pointer, never evidence.
-7. **Fan in.** Compare `git diff --name-only <base>...<b>` with the slice's
-   SCOPE: any file outside it stops the fan-in with a report. Then
-   `workit ledger check --branch <b>` for each slice; restack
-   stacked slices with `workit stack sync`. Only you touch topology: workers
-   never rebase, retarget or merge. Then workit-ship.
+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.
 
 ## Example
 
@@ -58,5 +66,6 @@ counts; SCOPE: `src/routes/usage.ts`, `test/usage.test.ts`; VERIFY:
 ## Check
 
 ```sh
+workit fanout check                # exit 0: in scope, no conflicts, landing order printed
 workit ledger check --branch <b>   # per slice: accepted (current, passing, independent)
 ```

package/skills/fanout/references/brief.md

@@ -12,6 +12,7 @@ CONTEXT: <pointers: spec section, ledger decisions, the neighbour file to imitat
 ACCEPTANCE:
   - Given <state>, When <action>, Then <observable result>
 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>
 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,
@@ -34,12 +35,56 @@ ACCEPTANCE:
   - Given 3 runs today and 1 yesterday, When GET /v1/usage, Then the last two entries are {"runs":1} and {"runs":3}
   - Given no auth header, When GET /v1/usage, Then the status is 401
 VERIFY: `workit check test`; verify-api feature "usage"
+TIER: standard
 TIMEBOX: 45 minutes
 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
 ```
 
+## Plan file
+
+`workit fanout plan <plan.json>` records the slices before any spawn. Each
+slice carries the brief fields the plan checks (goal, scope, acceptance,
+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"`.
+
+```json
+{
+  "name": "usage",
+  "trunk": "main",
+  "slices": [
+    {
+      "id": "usage-endpoint",
+      "branch": "feature/usage-endpoint",
+      "tier": "standard",
+      "scope": ["src/routes/usage.ts", "src/queries/usage.ts", "test/usage.test.ts"],
+      "owns": ["package.json"],
+      "goal": "GET /v1/usage returns the run count per UTC day for the last 7 days",
+      "acceptance": ["Given no auth header, When GET /v1/usage, Then the status is 401"],
+      "verify": ["workit check test"],
+      "forbidden": ["no edits outside SCOPE", "no rebase or force-push"],
+      "context": "docs/usage/spec.md Behavior",
+      "timebox": "45 minutes"
+    },
+    {
+      "id": "usage-docs",
+      "branch": "docs/usage",
+      "tier": "mundane",
+      "dependsOn": ["usage-endpoint"],
+      "scope": ["docs/usage/**"],
+      "goal": "The API guide documents GET /v1/usage",
+      "acceptance": ["Given the guide, When a reader looks up usage, Then the response shape is shown"],
+      "verify": ["workit check docs"],
+      "forbidden": ["no edits outside SCOPE"]
+    }
+  ]
+}
+```
+
 ## Worker rules (paste into the brief when the host has no implementer agent)
 
 1. First command. `MODE: new`: `workit git branch <branch> --base <base>` (the