Generated from cat-harness/skills/conduct/conduct-core/hand-back-to-discussion.md — do not edit here. Typed contract: schema reference.

✎ Edit this page’s source

Hand back to the discussion

The procedure behind Process_HandBackToDiscussion. It joins two rules that already bind: ask-the-person (how a question is put) and the relay paragraph of interaction-modality §4.1 (a relayed question says where the answer goes). This skill is the missing step between them: who puts the question, and how the answer gets back.

Why

A card posted only in a sibling’s own thread is not seen by the person, who is talking with the discussion agent elsewhere; the decision stalls, or reaches the person only by reconstruction. A feedback channel in play (a review sheet, an issue) is used as well.

The two roles

rolewhodoes
Discussion agent (session-coordinator)the agent the person is talking with right now: a project coordinator, the parent of a subagent, the session that spawned a swarmshows the hand-back to the person, asks with ask-the-person, marks every copy answered, routes the answer back
Sibling (sibling-session)any agent the discussion agent spawned, or one working beside it on the same goal: a project thread, a subagent, a workflow agent, a cloud sessioncomposes the hand-back once, with the analysis it alone has, and acts on the answer

You are a sibling when your brief names a discussion agent, or when you were started by another agent while a person was talking with it. A sibling that is not sure hands back anyway: one extra copy costs a line, and a missed card costs a stalled decision.

The brief names the discussion (spawning agent)

An agent that spawns a sibling during a live discussion puts the discussion link in the brief (definitions.discussion of the input schema): who the discussion agent is, how to reach it, the standing card rules, and any feedback channel in play (a review sheet’s id and tab, an issue). See process-state §”A coordinator that briefs a thread”. A sibling has nothing else that tells it.

Input and output

The contract is input.schema.json and output.schema.json.

  • In (the hand-back): from (title, link, process), to (the discussion link), kind (decision, question, context, result, blocker), a one-sentence summary, ask (the ask-the-person input, unchanged, for a decision or question), context (for the others), links, channels (always discussion, plus any of own-thread, project-chat, review-sheet, github-issue, github-pr), answerRoute, blocking, and supersedes when it replaces an earlier one.
  • Out (the record): shown (every copy, discussion first), state (open, answered, withdrawn, superseded, informed), the ask-the-person output, chosen, quote, answeredIn, marked (the strike-through edit per copy) and deliveredBack (proof the answer reached the sibling, with citesPerson).

Steps — sibling

  1. Compose once. A question is the full ask-the-person input: what will differ, context, every option lettered with a one-line trade-off, the recommendation and why, what happens with no answer. The discussion agent must be able to show it without opening your thread. Context, a result or a blocker gets the same test.
  2. Show it where you are. Post it in your own thread too (chat text, then the card), so the tappable card sits beside the work. Your own thread is never the only copy.
  3. Mirror it to the feedback channel in play. When a review sheet governs the work, write the “Decision needed” block into the row’s agent column and set Agentic status to Needs you (the document layer’s review-sheet-script skill, §”A question to people goes in the sheet”). An issue or PR in play gets a comment. These are extra copies, never instead of the discussion.
  4. Hand back to the discussion agent with the host’s route:

    hostroute
    Claude projects threadmessage_coordinator (or message_thread to the discussion thread), the hand-back as plain prose in the schema’s order: summary, question, lettered options with trade-offs, recommendation, if silent, link to your thread
    subagent (Agent tool, workflow agent)your final report: the hand-back as a fenced json block that validates against the input schema, then a one-line summary. You cannot reach the person; the parent asks
    sibling sessionSendMessage to the discussion session
    none of thesea comment on the issue or PR the discussion is about, and say so in your own thread
  5. Keep working on the recommended option where it can be undone; stop where it cannot (blocking: true).
  6. Act on the answer when it comes back. Only an answer that carries the person’s own words (a cited message, a card tap, a Blue-column cell) is their approval. A paraphrase from another agent is not.

Steps — discussion agent

  1. Show it in the discussion, saying it comes from the sibling (title and link) and that you will pass the answer on. A question goes through Process_AskThePerson unchanged: the chat text in full first, then the card with the same letters. Never “see the card in thread X”.
  2. Context, a result or a blocker that needs no answer: post it, state informed, done.
  3. Take the answer from any copy. A tap on your card, a tap on the sibling’s card, or a Blue-column answer in the sheet all count. Take the first, and treat a later disagreeing answer as a new question.
  4. Route it back on answerRoute, attaching the person’s own message by id where the host allows (citesPerson: true).
  5. Mark every copy answered. A chat copy keeps its text: strike the question through and add [Edit: <letter> chosen by <who>, <time>]. A card you posted is closed with the chosen option. A sheet’s “Decision needed” block is replaced by the decision and who made it, and Agentic status moves on. A withdrawn or superseded hand-back is marked the same way with the reason.
  6. A rule-level answer goes into the governing skill in the same turn (symbiotic-interaction §2).

Anti-patterns

  • A card only in the sibling’s thread.
  • A hand-back that says “see my thread”. A pointer is not the question.
  • The discussion agent rewriting the options. The sibling did the analysis; reword for the person if needed, but keep the letters and the recommendation, and say so if you change one.
  • The sheet as the only copy. People on the committee see the sheet; the owner in the discussion may not be looking at it.
  • An answer that never reaches the sibling. The person answered once; the sibling must not ask again.

Input and output contracts

What this skill takes and gives, as a class diagram drawn from its JSON Schema contracts by the schemas viewer’s own renderer. Each box links to its definition; each type to its specification.

input [1..1]output [1..1]from [1..1]links [0..*]answerRoute [1..1]options [2..4]shown [1..*]marked [0..*]deliveredBack [1..1]asked [1..1]pages [0..*]to [1..1]ask [0..1]channels [1..*]ask [0..1]stagingLinks [0..1]stagingLinks [0..1]hand-back-to-discussion«skill»hand-back-to-discussioninput : HandBackToDiscussionInput [1..1]output : HandBackToDiscussionOutput [1..1]HandBackToDiscussionInput«json-schema»HandBackToDiscussionInputfrom : HandBackToDiscussionInput.from [1..1]to : discussion [1..1]kind : "decision" | "question" | "context" | "result" | … [1..1]summary : string [1..1]ask : askThePersonInput [0..1]context : string [0..1]links : HandBackToDiscussionInput.links[] [0..*]channels : channel[] [1..*]answerRoute : HandBackToDiscussionInput.answerRoute [1..1]blocking : boolean [1..1]… 1 moreHandBackToDiscussionInput.from«json-schema»HandBackToDiscussionInput.fromtitle : string [1..1]link : string [1..1]process : string [0..1]HandBackToDiscussionInput.links«json-schema»HandBackToDiscussionInput.linkstitle : string [1..1]url : string [1..1]HandBackToDiscussionInput.answerRoute«json-schema»HandBackToDiscussionInput.answerRoutehow : "thread-message" | "send-message" | "return-value"… [1..1]target : string [1..1]discussion«json-schema»discussionagent : string [1..1]how : "coordinator-message" | "thread-message" | "send-m… [1..1]rules : string[] [0..*]channel«json-schema»channelkind : "discussion" | "own-thread" | "project-chat" | "r… [1..1]spreadsheetId : string [0..1]tab : string [0..1]row : string [0..1]column : string [0..1]repo : string [0..1]number : integer [0..1]askThePersonInput.options«json-schema»askThePersonInput.optionsletter : string [1..1]label : string [1..1]does : string [1..1]pro : string [1..1]con : string [1..1]downstream : string [1..1]reversibility : string [1..1]askThePersonInput«json-schema»askThePersonInputdecides : string [1..1]context : string [1..1]glossary : object [1..1]options : askThePersonInput.options[] [2..4]recommends : string [1..1]because : string [1..1]ifSilent : string [1..1]question : string [1..1]othersPending : integer [1..1]reversible : boolean [1..1]HandBackToDiscussionOutput«json-schema»HandBackToDiscussionOutputshown : HandBackToDiscussionOutput.shown[] [1..*]state : "open" | "answered" | "withdrawn" | "superseded"… [1..1]ask : askThePersonOutput [0..1]chosen : string | null [0..1]quote : string | null [0..1]answeredIn : "discussion" | "own-thread" | "project-chat… [0..1]marked : HandBackToDiscussionOutput.marked[] [0..*]deliveredBack : HandBackToDiscussionOutput.deliveredBack [1..1]stagingLinks : stagingLinks [0..1]HandBackToDiscussionOutput.shown«json-schema»HandBackToDiscussionOutput.shownchannel : "discussion" | "own-thread" | "project-chat" |… [1..1]ref : string [1..1]card : string | null [0..1]HandBackToDiscussionOutput.marked«json-schema»HandBackToDiscussionOutput.markedref : string [1..1]edit : string [1..1]HandBackToDiscussionOutput.deliveredBack«json-schema»HandBackToDiscussionOutput.deliveredBackhow : "thread-message" | "send-message" | "return-value"… [1..1]target : string [1..1]ref : string [0..1]citesPerson : boolean [0..1]at : string [1..1]askThePersonOutput.asked«json-schema»askThePersonOutput.askedchat : string [1..1]card : string | null [1..1]askThePersonOutput«json-schema»askThePersonOutputasked : askThePersonOutput.asked [1..1]outcome : "answered" | "silent" | "dismissed" [1..1]chosen : string | null [1..1]quote : string | null [1..1]defaultTaken : boolean [1..1]rule : string [0..1]stagingLinks : stagingLinks [0..1]stagingLinks.pages«json-schema»stagingLinks.pagestitle : string [1..1]before : string [0..1]after : string [0..1]summary : string [0..1]stagingLinks«json-schema»stagingLinksbranch : string [1..1]slug : string [1..1]branchUrl : string [1..1]pr : integer [0..1]mainBaseUrl : string [1..1]stagingBaseUrl : string [1..1]pages : stagingLinks.pages[] [0..*]missing : string[] [0..*]

Processes that run this skill

This skill has its own process: Hand back to the discussion.

BPMN diagram: Hand back to the discussion

processstep(s) that name it
Ask the personHand back to the discussion
Hand back to the discussionCompose the hand-back and post it in own thread; Mirror it to the feedback channel; Hand it back to the discussion agent; Post it in the discussion; Ask the person (calls a sub-process); Route the answer back, quoted; Mark every copy answered; Act on the answer

Provenance (2)

Who decided, when, and under which work item. This record was moved out of the text of the page.

Why

  • owner-decision cat-harness#861 2026-10-31 owner
    Owner, 2026-10-31: "sublings not raising cards to main. update process/skills when agent spawn is run in interactive agent-human discussion that that sibling of discussion agent will make sure to pass card/structured Q&A/context/.. back to the dsicussion agent with the human. if other fedbcak mechanism in play like tools such as google sheets that can enage as well then should also be avialbe to use" (cat-harness#861).
  • history 2026-09-22
    That day several sibling threads posted decision cards only in their own thread. The person was in the project chat, talking with the coordinator, and saw none of them until the coordinator found each one and relayed it by hand. A card nobody sees is a decision that stalls, and one relayed by reconstruction is the 2026-09-22 failure in interaction-modality again.

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