Hand Back To Discussion

Skill id: hand-back-to-discussion

Generated from JSON Schema — do not edit by hand. Run bun run cat-harness-tools/scripts/gen-schema-docs.ts.

Input

One hand-back from a sibling agent (spawned, or working beside the discussion) to the discussion agent: the agent that is talking with the person right now. It carries a card, a question, context, a result or a blocker, complete enough that the discussion agent can put it in front of the person without opening the sibling’s thread. A question or decision carries the ask-the-person input unchanged, so the card the person sees is composed once, by the agent that did the analysis.

FieldTypeRequiredDescription
fromobjectyesThe sibling that hands back.
toanyyes
kind"decision" | "question" | "context" | "result" | "blocker"yesdecision and question need the person’s answer and carry ask. context, result and blocker inform; a blocker that needs the person to act is a decision, not a blocker.
summarystringyesOne sentence that stands alone: what the person needs to know or choose. (minLength: 1, maxLength: 300)
askanynoThe composed question, exactly as ask-the-person takes it. Required for decision and question.
contextstringnoFor context, result and blocker: what happened, what it touches and what happens next, every id glossed.
linksarraynoPRs, issues, staging pages and files the hand-back is about, each with a title.
channelsarrayyesEvery place the hand-back is shown. The discussion is always one of them; a review sheet or an issue is an extra copy, never the only one.
answerRouteobjectyesHow the answer reaches the sibling again. An answer typed at the discussion does not reach the sibling by itself.
blockingbooleanyestrue when the sibling has stopped and waits on the answer; false when it keeps working on the recommended option.
supersedesstringnoThe id of an earlier hand-back this one replaces; the discussion agent withdraws that card.

from

FieldTypeRequiredDescription
titlestringyesThe sibling’s thread or task title, as the person would recognise it. (minLength: 1)
linkstringyesA link to the sibling’s thread, session or PR, so the person can open it for more. Never the only place the content is. (minLength: 1)
processstringnoThe process and step the sibling is in (process-state), or “none”.
FieldTypeRequiredDescription
titlestringyes
urlstringyes

answerRoute

FieldTypeRequiredDescription
how"thread-message" | "send-message" | "return-value" | "issue-comment" | "sheet"yesthread-message: the host’s message-to-thread tool, with the person’s message attached by id. send-message: a sibling session’s inbox. return-value: the sibling is a subagent and the answer goes into its next prompt. issue-comment and sheet: the sibling reads it there.
targetstringyesThe thread id, session id, issue or sheet row the answer goes to. (minLength: 1)

Raw schema · ✎ Edit

Output

The record of one hand-back: where it was shown, its state, the person’s answer quoted, how every copy was marked answered, and proof the answer reached the sibling. A dismissed card is not an answer.

FieldTypeRequiredDescription
shownarrayyesOne entry per copy, the discussion’s first.
state"open" | "answered" | "withdrawn" | "superseded" | "informed"yesopen: waiting. answered: the person chose, in any channel. withdrawn: the question no longer needs an answer. superseded: a later hand-back replaced it. informed: a context, result or blocker that needed no answer was shown.
askanynoThe ask-the-person output, when the hand-back carried a question.
chosenstring | nullnoThe letter chosen; null unless answered. (pattern: ^[A-D]$)
quotestring | nullnoThe person’s answer verbatim, with who, when and the message id or sheet cell it came from.
answeredIn"discussion" | "own-thread" | "project-chat" | "review-sheet" | "github-issue" | "github-pr" | nullnoWhich copy the answer came from.
markedarraynoHow each copy was closed once answered or withdrawn. A chat copy keeps its text: the question is struck through and “[Edit: chosen by ,
deliveredBackobject | nullyesProof the answer reached the sibling; null only while open or for state informed.
stagingLinksanynoWhen the question asks the person to look at changed pages: the staging preview, one deep link per changed page with the same page on main, shown in the chat copy. When there is no preview, say so in missing. Rule: cat-harness skills/authoring/content-lifecycle/feedback-deep-links.md.

shown[]

FieldTypeRequiredDescription
channel"discussion" | "own-thread" | "project-chat" | "review-sheet" | "github-issue" | "github-pr"yes
refstringyesMessage id, card id, sheet cell (tab!header/row key) or comment URL. (minLength: 1)
cardstring | nullnoThe card’s id when this copy offered one.

marked[]

FieldTypeRequiredDescription
refstringyes
editstringyesThe text applied, e.g. “Which layout? [Edit: A chosen by litlfred, 2026-10-31 15:50Z]”. (minLength: 1)

Raw schema · ✎ Edit


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev