Comments are useful when they change what we teach. “Too expensive” might mean someone needs a cheaper product, or it might mean we explained the wrong solution. We’ll use portrait-lighting questions to show how to keep those needs separate and save a source trail we can revisit.
Kabo, an AI agent for creator research, retrieves the public comments; Codex checks our existing answers before assigning each question a response.
Prepare the answer map and comment scope
[ ] video-links.txt — Public videos whose comment sections are relevant to our question. [ ] research-question.md — The viewer obstacle we want to understand. [ ] previous-titles.md — Existing answers and lessons to avoid duplicating. [ ] theme-rules.md — Definitions for request, correction, experience and unclear. [ ] our-demos.md — Rooms, equipment and examples we can film ourselves. [ ] lesson-summaries.md — Short notes describing the questions existing videos actually answer.
Connect Kabo inside the project
Install Kabo in Codex, complete sign-in and open a new task so the tools refresh. Keep the task in the content folder named below.
Build an answer map from what we already published
Our portrait-lighting channel already has an equipment guide. Before grouping comments into themes, ask Codex to read the existing answers and state what each actually covers. A familiar title is not proof that a specific question has been answered.
The deliverable is a response queue: link an existing explanation, make a short clarification, film a new demonstration or hold the question until we understand it.
Read previous-titles.md and the supplied lesson summaries. For each existing answer, state the question it covers and any known limitation. Create response options: existing answer, short clarification, new demonstration and unresolved. Do not infer full video coverage from a title alone.
Save the retrieved comments with their sampling rules
Use Kabo’s ready public comment tools for the chosen URLs. Keep source references, sort order, pagination limits and missing replies in comments-raw.csv. Tell Codex not to overwrite that evidence file when it groups themes. Public comments reflect a self-selected sample.
Three questions, three different responses
Illustrative routing decisions for the lighting channel:
- “Which modifier did you use?” If the existing equipment guide identifies it, link that answer after checking.
- “Where does the light go in a low-ceiling room?” A new placement demonstration may be needed; the buying guide is not an answer.
- “It still looks wrong.” Ask what result or setup the person means before inventing a lesson.
The wording here is authored for the example. When we run it, every queue entry retains the actual retrieved comment reference.
Route the question and explain the choice
Use Kabo’s retrieved sample with source and coverage notes. For each distinct question, ask Codex to compare the answer map before assigning a response. Combine duplicates only when they need the same answer; similar words can hide different problems.
The queue needs a reason and a next action. Frequency can help organize the collected sample, but it is not the reason every question deserves a new video.
From comments-raw.csv and the reviewed answer map, write response-queue.md with question paraphrase, actual source references, matching existing answer, response type, reason and next action. Use sample-only counts where helpful. Keep ambiguous questions unresolved. Create a new demonstration brief only when the current library does not answer the need.
Work the queue from small answers to new filming
Verify the linked answers, draft the short clarifications and choose one new demonstration. A low-ceiling placement lesson needs owned room footage and a visible comparison. Keep that requirement in its brief rather than turning every comment theme into a script.
For a group that needs shared classification rules, the Claude Code comment workflow shows a small calibration exercise.
Separate low-ceiling problems from equipment-budget questions. Keep the room demonstration as a video and move simple product substitutions into the FAQ.
Work the response queue before booking another shoot
Open the response queue in Google Sheets if a collaborator needs to assign owners. Use the ideas guide to develop the selected demonstration, then the script guide for narration. Keep unresolved questions in the queue; do not turn them into confident public replies.
Worked examples are illustrative. Product screenshots show existing Kabo web results, not a run of the example in this guide. Use your own materials and the evidence returned in your task.