apply
Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a…
Summarize the named documents to the agreed length, one sentence at a time, each backed by quotations, citing every part or leaving it out with a reason — writing .blueprint/summary.json and changing no document.
$ npx -y skills add receptron/mulmoterminal --skill summarize --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/summarizeContext preview
The summary Claude sees to decide when to auto-load this skill.
Summarize the named documents to the agreed length, one sentence at a time, each backed by quotations, citing every part or leaving it out with a reason — writing .blueprint/summary.json and changing no document.
name: blueprint-summarize-summarize description: "Summarize the named documents to the agreed length, one sentence at a time, each backed by quotations, citing every part or leaving it out with a reason — writing .blueprint/summary.json and changing no document."
`.blueprint/answers.json` names the documents (`documents`, one path per line), how long the summary may be (`length`), who reads it (`reader`, may be empty) and what they most want to know (`focus`, may be empty). Read every document in full. The person may not be an engineer: say what you do in plain words.
Change nothing in the repository: the documents stay exactly as they are. Write only under `.blueprint/`.
Run `sh <base pack>/checks/chaff.sh tree <file> --format json` on each document. Its **parts** are its articles (`kind` `article`) when it has any; otherwise its sections at the first level with more than one (under a single title heading, the sections below it). Every part is either cited by some sentence of the summary or left out on purpose, with a reason the person can judge — never dropped silently.
{
"sentences": [
{
"text": "経理部の確認が済んだ申請は、毎月25日に給与口座へ振り込まれる。",
"citations": [{ "source": "keihi.md", "address": "h1.3", "quote": "毎月25日にまとめて給与口座へ振り込みます" }]
}
],
"omitted": [{ "source": "keihi.md", "address": "h1.4", "why": "例外の手続きで、この読み手には要らないため" }]
}`focus` first when it names something.
it, `address` from the tree (the paragraph or item the words are in, or the part itself), `quote` copied character for character. The check runs `chaff cite` on every one.
the name of a place it cites, such as 第4条): the check refuses any other. Do not add up, convert or round.
outnumber the sentences, one sentence may cite several parts, or a part the reader does not need may be left out in `omitted` — with a reason.
`node <usecase pack>/checks/summary.mjs` (with `BLUEPRINT_BASE` and `BLUEPRINT_USECASE` set to the pack folders from your prompt) passes. It writes `.blueprint/summary.txt`, the summary with where each sentence comes from, which the person reads before the report.
Run multiple coding-agent sessions in parallel — and see which one needs you. A browser terminal for parallel AI coding agents: several sessions side by side, each in its own cell, with the one that needs you marked in colour.
Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a…
Measure what chaff reports on the named documents today, as the kind the person chose, and propose the setup — changing nothing…
Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the documents do…
Add the approved answers to FAQ.md when the person chose to keep them, after what it already holds; change nothing otherwise.
Build the spec's operations as the Worker's API, with validation and tests.