Generated from cat-harness/skills/conduct/conduct-core/ask-the-person.md — do not edit here. Typed contract: schema reference.

✎ Edit this page’s source

Ask the person

The procedure behind Process_AskThePerson. Every diagram step that puts a choice to a person calls that subprocess, and the subprocess’s tasks name this skill. The rule itself, and why, is the box at the top of interaction-modality; this skill is how to carry it out.

Input and output

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

  • In: decides (what will differ), context (why now, what it touches, what happens next), glossary, two to four options each with a letter, label, does, pro, con, downstream and reversibility, the recommends letter and because, ifSilent, the question, othersPending and whether the step is reversible. The fields match DecisionRequestSchema in decision-request.ts, plus the letter and the context. Nothing is optional.
  • Out: asked.chat and asked.card (the two copies), outcome (answered, silent or dismissed), chosen (a letter), quote (the answer verbatim), defaultTaken, and rule when the answer became a rule.

Steps

  1. Compose the input. Can the reader answer without opening anything? If not, it is not ready.
  2. Write it in the chat, whole: context, every option with its letter, one-line explanation and trade-off, the recommendation marked, and what happens with no answer. This is the copy that lasts, because an answered card shows only the choice.
  3. Offer the card with the same letters and labels, recommended one marked. This holds for request_decision even though that tool’s own text says not to repeat the question. No card tool: say so in the chat.
  4. Wait for the tap; keep working on the recommended option where that can be undone. Never ask for a typed reply.
  5. Not the one talking with the person? If you are a sibling (a project thread, a subagent or a session spawned while someone else holds the discussion), steps 2 and 3 in your own channel are not enough: hand the composed input back with hand-back-to-discussion, so the discussion agent asks it where the person is, and the answer comes back to you. Your own thread is never the only copy.
  6. Return the output. A dismissal is not an answer. A rule-level answer is written into the governing skill in the same turn (symbiotic-interaction §2).

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]options [2..4]asked [1..1]pages [0..*]stagingLinks [0..1]ask-the-person«skill»ask-the-personinput : AskThePersonInput [1..1]output : AskThePersonOutput [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]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]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]AskThePersonOutput.asked«json-schema»AskThePersonOutput.askedchat : string [1..1]card : string | null [1..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: Ask the person.

BPMN diagram: Ask the person

processstep(s) that name it
Ask the personCompose the full question; Discuss it with the person (calls a sub-process)
Hand back to the discussionCompose the hand-back and post it in own thread; Ask the person (calls a sub-process)
Saturation meta-merge: land the ready PRs when the runners are fullDry-run, then ask the owner naming every PR

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