無料GitHub で公開

deliverable-intake

Turns raw captures (dictated braindumps in a deliverable's inbox/, or recent macwhspr dictation-log entries) into proposed planning-wiki changes, shown as one unified diff. Classifies each statement as a decision, evidence claim, question, task, or dropped item, traces it to its capture paragraph, tags unconfirmed names, numbers, and citations UNRESOLVED, and writes decisions only with the author's assent. Edits only the planning wiki, never source files. Use when asked to intake, absorb notes, or process the inbox, or after dictating notes from a talk, meeting, or reading session.

scdenney/open-science-skills

インストール方法を見る

含まれるファイル（1）

SKILL.md5.5 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Deliverable intake

Full guide: docs/deliverable-pipeline.md in the repository.

The author thinks out loud; the wiki stays authoritative. This skill is the seam between the two. It reads captures verbatim, proposes where each statement belongs, and applies nothing the author has not seen.

Inputs

The nearest deliverable.yml upward from cwd (or the path given). Read it, then planning_dir/00-README.md and every file that index names. That is the current state of the wiki; the proposal is a diff against it.
inbox/*.md that do not end in .done.md, oldest first. A capture is read verbatim and never edited.
--from-log N: show the last N entries of ~/.config/macwhspr/cleanup_log.jsonl ({ts, raw, cleaned} pairs) as a numbered list with the first line of each, and ask which to import. An imported entry is written to inbox/YYYY-MM-DD-HHMM-log.md with the cleaned text (the raw text appended under a  marker) before anything else happens. Nothing is imported without being named.

Classify, then trace

Walk the capture paragraph by paragraph. Each statement gets exactly one class:

Class	Goes to	Needs assent?
decision	the wiki file that owns the topic (`00-README.md` "Decisions recorded here", or the numbered file)	yes, always
evidence claim	the wiki file for the section it supports, marked with the capture reference	no, but a claim naming a source that is not in `sources_of_truth` or the bib is written as `UNRESOLVED: <claim>`; when the manifest names a `knowledge_base`, the report lists each such source as a `process-source` candidate (drop the PDF in `sources/unprocessed/`) so intake feeds the knowledge base rather than bypassing it
question	`08-open-questions.md`, open list	no
task	`08-open-questions.md` under a `Tasks` heading; one due before the next session is also named in the report, so the closure step carries it into HANDOFF	no
dropped	nowhere; listed in the report with the reason (duplicate, already resolved, off-topic)	no

Every proposed line carries a trace: (inbox/2026-09-10-debrief.md ¶3). A capture paragraph that yields no proposal is listed as dropped with its reason, so the author can see the capture was read whole.

Names, dates, numbers, and citations that the capture states but the wiki cannot confirm stay as dictated and are tagged UNRESOLVED. Do not correct a dictated name against a guess; do not invent a citation to match a claim; do not resolve a number from memory.

Propose

Produce one unified diff across the wiki files (new files included) plus the dropped list. Show it. Then put the decisions to the author as a numbered list, each with the sentence that would be written and where; use AskUserQuestion when there are three or fewer, a numbered list otherwise.

Apply

Once the author has seen the diff, apply the non-decision hunks and each decision they approved, then rename the capture to *.done.md. Do not edit any existing HANDOFF.md entry, today's included; the intake is recorded by the closure step (/oss:finished) as Intake: <capture> -> <n> decisions, <n> claims, <n> questions, <n> tasks, <n> dropped, and if the session ends without closure the renamed capture and the wiki diff are the record. Record which capture paragraphs were promoted (a  line at the end of the .done.md file) so a partially accepted capture is never promoted twice. On refusal of any decision, leave that line out and keep the capture unrenamed until the author says otherwise.

Report

Five lines: captures read; counts by class; UNRESOLVED items (each with what would resolve it); decisions applied; what to run next (/oss:deliverable-lint if the wiki changed materially, otherwise nothing).

Notes

One worker, no subagents; a cheap model suffices.
A reaction to a lint report is a capture like any other: dictate it into inbox/, then intake it; findings the author accepts become tasks, findings they reject go under a Rejected findings heading in 08-open-questions.md (the authoritative wiki, not NOTES.md) with the finding id and one line of reason, so the next lint does not raise them again.
Register vocabulary as it appears: a proper noun the dictation mangled twice belongs in ~/.config/macwhspr/vocab.md (offer, never append silently).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

advisor

無料

Consults Fable as an independent, read-only reviewer at an effort the caller matches to the question. The calling session (usually Opus, or Haiku) holds the task and escalates one decision point. Use before committing to an interpretation or a substantial piece of writing or analysis, when stuck or not converging, when changing approach, or as a final check on a finished task. Fallback for when the native advisor tool is unavailable. Not for a session already running Fable.

日本語の概要は準備中です。原文の説明を表示しています。