summaryrefslogtreecommitdiff
path: root/skills/pi-review-panel
diff options
context:
space:
mode:
authorIgor Soarez <igor@soarez.org>2026-10-21 12:39:32 +0100
committerIgor Soarez <igor@soarez.org>2026-10-21 12:39:32 +0100
commit9faef45275e9ab24e10bfed878f6890ba76a1bb0 (patch)
tree0bbeb699d94186ca545e782808f09a00611a9742 /skills/pi-review-panel
parent32123f167dd5a7cdcbdaf6e5c144f40654d236fc (diff)
pi-subagent: opt-in sessions, to follow up, resume after a timeout, or fork
run-agent.sh still runs with --no-session by default. --session saves the run as session <name> under <workdir>/sessions/; --followup TEXT sends the next message in it, from any provider and model; --fork FROM starts <name> as a copy of FROM. A follow-up or fork inherits --tools, --thinking, --cwd and --context-files, so a read-only subagent stays read-only, and the earlier round's files move to <name>.round<N>.*. Sessions are opened by file path: by id, pi looks only among sessions started in the current directory and otherwise silently creates an empty one, exit 0. A fresh retry moves the old session aside, since pi would resume it given the same id. pi-review-panel launches members with --session, so a contradiction can be put to both reviewers before it is settled; verdicts are still tallied from the original reviews. From dot request 20261021-123436-work-laptop-d0adf2.
Diffstat (limited to 'skills/pi-review-panel')
-rw-r--r--skills/pi-review-panel/SKILL.md21
1 files changed, 19 insertions, 2 deletions
diff --git a/skills/pi-review-panel/SKILL.md b/skills/pi-review-panel/SKILL.md
index f850ebb..f50abac 100644
--- a/skills/pi-review-panel/SKILL.md
+++ b/skills/pi-review-panel/SKILL.md
@@ -74,10 +74,11 @@ State at the top of the final report exactly what was reviewed (commit range,
## 3. Run the panel
-All members at once, one line per row of the table:
+All members at once, one line per row of the table, with `--session` so that
+contradictions can be put back to the reviewers in §4:
```bash
-"$SA/run-agent.sh" --deliver "the full markdown review" "$P" fireworks "accounts/fireworks/models/kimi-k3" fw-kimi-k3 > "$P/out/_fw-kimi-k3.log" 2>&1 &
+"$SA/run-agent.sh" --session --deliver "the full markdown review" "$P" fireworks "accounts/fireworks/models/kimi-k3" fw-kimi-k3 > "$P/out/_fw-kimi-k3.log" 2>&1 &
# ...and so on for each member
```
@@ -90,6 +91,22 @@ the panel: the same model on the other provider usually keeps the coverage.
Verify first (pi-subagent §7): the reviews are raw material, and the places
where reviewers contradict each other are where the real answer usually is.
+Where two reviewers contradict each other on something that matters, follow
+each one up with the other's finding (pi-subagent §10) before you settle it:
+
+```bash
+"$SA/run-agent.sh" --followup "Another reviewer says: <finding, with its evidence>. \
+Check it against the code and say who is right, with the command and output \
+that decides it. End with: VERDICT: <same pair as before>" \
+ "$P" fireworks "accounts/fireworks/models/kimi-k3" fw-kimi-k3
+```
+
+Their replies sharpen the question; they don't answer it. A reviewer giving
+way is not proof — run the deciding experiment yourself either way, and tally
+verdicts from the original reviews, noting any that changed. Once a member has
+been followed up, its original review is `<name>.round1.md` and `<name>.md` is
+the reply.
+
The report:
- What was reviewed.