@iceinvein/agent-skills 0.6.0 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iceinvein/agent-skills",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Install agent skills into AI coding tools",
   "author": "iceinvein",
   "license": "MIT",

package/skills/index.json

@@ -283,7 +283,7 @@
     "name": "sluice",
     "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries seven rules as one-liners in the router and the full treatment in references read only on friction, and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what every dispatched agent cost. Claude Code only; conflicts with the superpowers plugin.",
     "type": "prompt",
-    "version": "0.3.0"
+    "version": "0.4.0"
   },
   {
     "name": "temporal-coupling-detector",

package/skills/sluice/SKILL.md

@@ -109,8 +109,8 @@ dependency edges and `Touches` says what cannot overlap, so which tasks may
 run at once is derivable rather than guessed. Fan out wherever that graph
 allows; serial is the fallback for where it doesn't, not the default.
 
-Then read `references/deep-channel.md` for the plan format, that stop,
-the dispatch rules, and when a task actually needs a reviewer. Three that
+Then read `references/deep-channel.md` for the plan format, that stop, the run
+record, the dispatch rules, and when a task actually needs a reviewer. Three that
 catch people out: concurrent implementers need a worktree each and the flip
 runs alone, review is tiered rather than automatic, and a `deep` run that
 cannot dispatch has to replace the review tier with something, not quietly

package/skills/sluice/references/deep-channel.md

@@ -107,6 +107,21 @@ review options are. Skipping it is how "review outstanding" first appears in
 the closing summary, at the one moment your partner can no longer do anything
 about it.
 
+## The run record
+
+A `deep` run outlives its own context, so what it learns has to sit on disk
+rather than in the session. Keep one file for the run and write it as you go.
+It holds what a stranger resuming tomorrow would need and you would otherwise
+be recalling: the base each task was dispatched from, each task with its status
+and its commits, the review decisions pre-flight settled and the reason each
+one was settled that way, and any finding belonging to a task other than the
+one that surfaced it.
+
+Where it goes follows the repo if the repo has a convention, and
+`docs/plans/YYYY-MM-DD-<topic>-record.md` if it does not. Assembling it at
+handback defeats it: a record written from memory is memory, which is the one
+thing the file exists to replace.
+
 ## Dispatch rules
 
 Read the plan as a graph before you read it as a list. `Needs` and `Offers`
@@ -121,8 +136,8 @@ Derive the sets at dispatch rather than writing wave numbers into the plan. A
 declared schedule is wrong the moment one task lands late or comes back with a
 blocking finding. A derived one just recomputes.
 
-- One `TaskCreate` per task, marked in progress then complete. That state
-  outlives compaction; your memory doesn't.
+- One line per task in the run record, marked in progress then complete as it
+  moves. That state outlives compaction; your memory doesn't.
 - Each task goes to a fresh agent with that task's text and nothing else.
   What this session accumulated is yours to hold, not theirs.
 - **Fan out wherever the graph allows.** Work that does not write is always
@@ -171,8 +186,8 @@ not the summary at the end where it reads as an excuse.
 Three things change. The plan stops being a brief for strangers and becomes
 your own worklist, which makes its handback the only outside read it will ever
 get rather than a formality on the way to dispatch. Task isolation is gone, so
-`TaskCreate` now carries all of the state that outlives compaction and matters
-more, not less. And fresh context is unavailable, which was the entire thing
+the run record now carries all of the state that outlives compaction and
+matters more, not less. And fresh context is unavailable, which was the entire thing
 review was buying.
 
 One thing does not change: the work still owes a review. Reading your own diff
@@ -225,8 +240,8 @@ a reviewer writes nothing, so it collides with nothing. The final review is
 the only one that waits, because it is the only one that needs everything to
 have landed.
 
-Record the base in the task's `TaskCreate` entry when you dispatch, before the
-agent's first commit lands. Recovering it afterwards is archaeology, and the
+Record the base against that task in the run record when you dispatch, before
+the agent's first commit lands. Recovering it afterwards is archaeology, and the
 answer you will guess at is `HEAD~1`, which `references/review.md` already
 names as the standing mistake.
 
@@ -260,8 +275,8 @@ Contracts mean tasks are built blind, so a reviewer reading Task 6 will
 sometimes be right about Task 2. That finding fits neither destination: Task
 6's agent cannot act on it, and it does not quietly become yours to fix.
 
-Record it on the earlier task's `TaskCreate` entry, and send it to that task's
-agent as well if that agent is still live. If it invalidates an `Offers` that
+Record it against the earlier task in the run record, and send it to that
+task's agent as well if that agent is still live. If it invalidates an `Offers` that
 later tasks have already built against, it has stopped being a finding and
 become a plan change, which is your partner's call rather than something to
 absorb into the next task's brief.

package/skills/sluice/scripts/run-stats.sh

@@ -95,9 +95,13 @@ SUMMARY="$(jq -s --argjson costs "$COSTS" '
       .message.content[]? | select(.type == "tool_use" and .name == "Skill")
       | select((.input.skill // "") == "sluice")
     ] | length > 0);
+  # A call carrying --transcript is reading another run rather than closing
+  # this one. Without that exception, a session working on the ledger
+  # clips its own run at the last session it tested against.
   def is_stats_call: (.type == "assistant") and ([
       .message.content[]? | select(.type == "tool_use" and .name == "Bash")
       | select((.input.command // "") | test("run-stats\\.sh"))
+      | select((.input.command // "") | test("--transcript") | not)
     ] | length > 0);
   # Waiting is any turn the partner had to take: a prompt, or an answer to a
   # question you put to them. Leaving the latter out understates the wait on

package/skills/sluice/skill.json

@@ -1,6 +1,6 @@
 {
   "name": "sluice",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries seven rules as one-liners in the router and the full treatment in references read only on friction, and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what every dispatched agent cost. Claude Code only; conflicts with the superpowers plugin.",
   "author": "iceinvein",
   "type": "prompt",