Generated from
cat-harness/skills/conduct/conduct-core/ask-the-person.md— do not edit here. Typed contract: schema reference.
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 fouroptionseach with aletter,label,does,pro,con,downstreamandreversibility, therecommendsletter andbecause,ifSilent, thequestion,othersPendingand whether the step isreversible. The fields matchDecisionRequestSchemaindecision-request.ts, plus the letter and the context. Nothing is optional. - Out:
asked.chatandasked.card(the two copies),outcome(answered,silentordismissed),chosen(a letter),quote(the answer verbatim),defaultTaken, andrulewhen the answer became a rule.
Steps
- Compose the input. Can the reader answer without opening anything? If not, it is not ready.
- 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.
- Offer the card with the same letters and labels, recommended one marked.
This holds for
request_decisioneven though that tool’s own text says not to repeat the question. No card tool: say so in the chat. - Wait for the tap; keep working on the recommended option where that can be undone. Never ask for a typed reply.
- 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. - 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:
cat-harness/schemas/skills/ask-the-person/input.schema.json - output:
cat-harness/schemas/skills/ask-the-person/output.schema.json
Processes that run this skill
This skill has its own process: Ask the person.
| process | step(s) that name it |
|---|---|
| Ask the person | Compose the full question; Discuss it with the person (calls a sub-process) |
| Hand back to the discussion | Compose 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 full | Dry-run, then ask the owner naming every PR |