Shared: unique review-package collateral names

skills/subagent-driven-development/SKILL.md

@@ -112,7 +112,7 @@ single-file mechanical fixes.
 
 Implementer subagents report one of four statuses. Handle each appropriately:
 
-**DONE:** Generate the review package (`scripts/review-package BASE HEAD /tmp/sdd-task-N.diff`, from this skill's directory; BASE is the commit you recorded before dispatching the implementer — never `HEAD~1`, which silently drops all but the last commit of a multi-commit task), then dispatch the task reviewer with that path.
+**DONE:** Generate the review package (`scripts/review-package BASE HEAD`, from this skill's directory — it prints the unique file path it wrote; BASE is the commit you recorded before dispatching the implementer — never `HEAD~1`, which silently drops all but the last commit of a multi-commit task), then dispatch the task reviewer with the printed path.
 
 **DONE_WITH_CONCERNS:** The implementer completed the work but flagged doubts. Read the concerns before proceeding. If the concerns are about correctness or scope, address them before review. If they're observations (e.g., "this file is getting large"), note them and proceed to review.
 
@@ -154,13 +154,13 @@ final whole-branch review. When you fill a reviewer template:
   floors, naming and copy rules, platform requirements) in the requirements
   you paste — a reviewer can only enforce what you hand them.
 - Hand the reviewer its diff as a file: run this skill's
-  `scripts/review-package BASE HEAD /tmp/sdd-task-N.diff` (or, without
-  bash: `git log --oneline`, `git diff --stat`, and `git diff -U10` for
-  the range, redirected to the file). The output never enters your own
-  context, and the reviewer sees the commit list, stat summary, and full
-  diff with context in one Read call. Use the BASE you recorded before
-  dispatching the implementer — never `HEAD~1`, which silently truncates
-  multi-commit tasks.
+  `scripts/review-package BASE HEAD` and pass the reviewer the file path
+  it prints (or, without bash: `git log --oneline`, `git diff --stat`,
+  and `git diff -U10` for the range, redirected to one uniquely named
+  file). The output never enters your own context, and the reviewer sees
+  the commit list, stat summary, and full diff with context in one Read
+  call. Use the BASE you recorded before dispatching the implementer —
+  never `HEAD~1`, which silently truncates multi-commit tasks.
 - Dispatch fix subagents for Critical and Important findings. Record Minor
   findings and move on — then paste the accumulated Minor findings into the
   final whole-branch review dispatch so it can triage which must be fixed
@@ -201,7 +201,7 @@ Implementer: "Got it. Implementing now..."
   - Self-review: Found I missed --force flag, added it
   - Committed
 
-[Write diff to /tmp/sdd-task-N.diff, dispatch task reviewer with the path]
+[Run review-package, dispatch task reviewer with the printed path]
 Task reviewer: Spec ✅ - all requirements met, nothing extra.
   Strengths: Good test coverage, clean. Issues: None. Task quality: Approved.
 
@@ -219,7 +219,7 @@ Implementer:
   - Self-review: All good
   - Committed
 
-[Write diff to /tmp/sdd-task-N.diff, dispatch task reviewer with the path]
+[Run review-package, dispatch task reviewer with the printed path]
 Task reviewer: Spec ❌:
   - Missing: Progress reporting (spec says "report every 100 items")
   - Extra: Added --json flag (not requested)
@@ -291,8 +291,8 @@ Done!
   dispatch prompt ("treat it as Minor at most") — the plan's example code is
   a starting point, not evidence that its weaknesses were chosen
 - Dispatch a task reviewer without a diff file — generate it first
-  (`scripts/review-package BASE HEAD /tmp/sdd-task-N.diff`) and name that
-  path in the prompt
+  (`scripts/review-package BASE HEAD`) and name the printed path in the
+  prompt
 - Move to next task while the review has open Critical/Important issues
 
 **If subagent asks questions:**