Generated from cat-harness/processes/process/hand-back-to-discussion.bpmn by gen-processes-viz.ts — do not edit here. All processes · cat-harness processes

Hand back to the discussion

Process_HandBackToDiscussion · strict · 8 step(s)

How a sibling agent gets a card, question, result, blocker or context in front of the person: through the discussion agent that is talking with them, never only in its own thread. The person’s answer comes back the same way.

INPUT AND OUTPUT: the hand-back-to-discussion skill’s schemas, schemas/skills/hand-back-to-discussion/input.schema.json (from, to, kind, summary, ask = the ask-the-person input, context, links, channels, answerRoute, blocking) and output.schema.json (shown, state, chosen, quote, answeredIn, marked, deliveredBack).

THE PERSON’S STEP is inside Process_AskThePerson, called by the discussion agent, so the asking rule (chat text first, then the card) holds here unchanged. A Blue-column answer in a review sheet is an answer to that same question.

BPMN diagram: Hand back to the discussion

How it connects

  • Called by: no call activity names this process
  • Calls: Ask the person
  • Names the hand-back-to-discussion skill without calling this process: Ask the person — activity-calls-skill-process asks whether each should be a call activity.
  • Presented on: no docs page section shows this diagram
  • Skill: hand-back-to-discussion
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
Siblingsibling-sessionAny agent that is not the one talking with the person: a project thread, a subagent, a workflow agent, a cloud session. It did the analysis, so it composes the hand-back.
Discussion agentsession-coordinatorThe agent the person is talking with right now. Shows the hand-back, asks, marks every copy answered and routes the answer back.

Steps

Every one of the 8 step(s) is documented.

steplaneskill / sub-processwhat it does
Compose the hand-back and post it in own thread
S_Compose
Siblinghand-back-to-discussion
ask-the-person
Compose it once, against the input schema: a question is the full ask-the-person input (what will differ, context, lettered options with a one-line trade-off each, the recommendation, what happens with no answer); context, a result or a blocker gets the same stand-alone test. Post it in your own thread too, chat text then card. Your own thread is never the only copy.
Mirror it to the feedback channel
S_Mirror
Siblinghand-back-to-discussionReview sheet: the “Decision needed” block in the row’s agent column, Agentic status Needs you (the document layer’s review-sheet-script skill). Issue or PR: a comment. An extra copy, never instead of the discussion.
Hand it back to the discussion agent
S_HandBack
Siblinghand-back-to-discussionBy the host’s route: message_coordinator or message_thread in Claude projects; the final report (a json block valid against the input schema) for a subagent; SendMessage for a sibling session. Then keep working on the recommended option where it can be undone, or stop if blocking.
Post it in the discussion
D_Inform
Discussion agenthand-back-to-discussionSay it comes from the sibling (title and link) and give the context or result in full. State informed.
Ask the person
D_Ask
Discussion agentcalls Ask the person
ask-the-person
hand-back-to-discussion
The sibling’s ask, unchanged in letters and recommendation, through Process_AskThePerson: the full chat text first, naming the sibling and that the answer will be passed on, then the card. A tap on the sibling’s own card or a Blue-column answer in the sheet answers it too; take the first.
Route the answer back, quoted
D_RouteBack
Discussion agenthand-back-to-discussionOn answerRoute, with the person’s own message attached by id where the host allows, so the sibling can treat it as the person’s approval. A paraphrase is never approval.
Mark every copy answered
D_MarkAnswered
Discussion agenthand-back-to-discussionChat copies keep their text: the question struck through and “[Edit: <letter> chosen by <who>, <time>]” added. Cards closed with the chosen option. The sheet’s “Decision needed” block replaced by the decision and who made it. Withdrawn or superseded hand-backs marked the same way, with the reason.
Act on the answer
S_Act
Siblinghand-back-to-discussion
symbiotic-interaction
Never ask the person again for what they answered. A rule-level answer goes into the governing skill in the same turn.

Decisions

Every one of the 2 decision(s) is documented.

decisionwhat decides itbranches
Feedback channel in play?
GW_Channel
yes when the brief or the work names a review sheet, issue or PR where the people concerned read; no otherwise.yes → Mirror it to the feedback channel
no → GW_ChannelJoin
Needs an answer?
GW_NeedsAnswer
yes for kind decision or question; no for context, result or blocker.yes → Ask the person
no → Post it in the discussion

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