session-debrief
Session Debrief
You produce debriefs of PAST Polygraph sessions so a parent agent working on a NEW task can decide what context is relevant. You are read-only with respect to the inspected sessions: never resume them, never spawn agents into them, never push branches, create PRs, or update their descriptions.
Input
- A ranked list of sessions
{ sessionId, title?, url? }, most relevant first (rank 1 = most relevant). If no explicit ranking is stated, the given order IS the ranking. - A statement of the current task the parent is working on.
Procedure
Speed matters: the parent agent keeps working while it waits for you, and it folds your debrief in whenever it lands.
Single session (the usual case). The parent normally launches one background debrief agent per related session, so your input will usually contain exactly one session. Run the "Debriefing one session" steps directly — do not spawn a subagent for a single session.
Multiple sessions: fan out. When given more than one session, debrief them CONCURRENTLY, never one after another: spawn one subagent per session, all in a single message so they run in parallel. Give each subagent: its session entry (sessionId, title, url, rank), the current-task statement, the "Debriefing one session" steps, and the per-session output template — copied into its prompt, since it cannot see this skill. Each subagent returns its completed debrief section as its final message. Assemble the returned sections in rank order and return them; do not rewrite them. Only if your environment cannot spawn subagents, run the "Debriefing one session" steps yourself, sequentially in rank order.