Studio Review Notes
The client note that writes itself
- review_notes_md
- review_notes_json
- summary
You know the note: "Here's v003 for review, 12 frames, 3 selected, 1 needs revision on the hair, next steps are cleanup and a lighting pass." Writing that by hand for every round is how review emails eat an hour. MKRStudioReviewNotes assembles it from the data you already have - give it a delivery plan and a selection set and it produces a structured Markdown summary plus JSON, with a headline, next steps, file suggestions, frame notes, and a status breakdown.
Mechanically it's a document builder: it takes delivery_plan_json (from MKRStudioDeliveryPlan), optionally a selection_manifest_json (from MKRStudioSelectionSet), your headline, your next_steps text, and then decides what sections to include based on three toggles - include_suggested_files (list the files being delivered), include_frame_notes (frame-by-frame notes from the selection), and include_status_breakdown (how many frames are SELECT/APPROVE/REVISE/etc). You write the two text fields; it writes everything else.
The inputs
- delivery_plan_json (required) - the identity of the review round.
- headline - the one-line summary, e.g. "v003 lookdev review".
- next_steps - your free-text action list.
- The three
include_*toggles - trim or expand the generated sections. - selection_manifest_json (optional) - for the frame notes and status breakdown to exist, this needs to come in; without it those sections have nothing to summarize.
- extra_notes (optional) - anything else you want appended.
What comes out
review_notes_md (the Markdown you'll paste anywhere), review_notes_json (structured form), and summary (a short JSON summary).
Installing it
Part of criskb/MKRShift_Nodes from Cris K B. ComfyUI Manager search "MKRShift_Nodes", or:
cd ComfyUI/custom_nodes
git clone https://github.com/criskb/MKRShift_Nodes
Restart. No pip requirements, no models.
Where it pays off
The magic is in the pipeline: plan + selection set → notes. If you're just feeding a plan in with no selection context, you'll get a clean note but no per-frame detail, which defeats half the point - so wire MKRStudioSelectionSet in. It's a text-generating node with no LLM involved, which is a feature: deterministic, instant, and never drifts into hallucinated summary. For clients who get a fresh note every round, this is the node that makes the rounds manageable.
Inputs (8)
| Name | Type | Default | Description |
|---|---|---|---|
| delivery_plan_json | STRING | — | |
| headline | STRING | — | |
| next_steps | STRING | — | |
| include_suggested_files | BOOLEAN | true | — |
| include_frame_notes | BOOLEAN | true | — |
| include_status_breakdown | BOOLEAN | true | — |
| selection_manifest_jsonopt | STRING | — | |
| extra_notesopt | STRING | — |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| review_notes_md | STRING | — |
| review_notes_json | STRING | — |
| summary | STRING | — |