Build a Book Companion That Produces a Useful Document

A useful book companion should produce something the reader can use in the situation your method addresses: a plan, a brief, a checklist, a draft, or a decision record. Define that artifact before writing the conversation that will produce it.

For each output, specify the reader, the moment of use, the information required, and the checks that make it ready for review. Include a clear way to mark missing facts. A polished document with invented details is not a completed task.

This walkthrough uses a fictional author of a practical family-history book. Their proposed skill helps a reader prepare one interview plan. The example is about designing an author skill's deliverable, not replacing the work of an oral historian or demonstrating an actual AI run.

“Ask open-ended questions and listen carefully” may be useful advice. An interview plan goes further: it names a focus, lists a few questions tied to that focus, supplies optional follow-ups, and identifies what the interviewer must confirm before starting.

The artifact should reduce the remaining work in an honest way. It can help a reader prepare; it cannot conduct a future conversation, establish another person's consent, or guarantee the memories they will share.

For your book, write the output promise in a sentence: “After using this skill, the reader has a draft ___ that they can review with ___ before ___.” If those blanks are difficult to fill, the deliverable may still be too vague.

Avoid selecting a format merely because the AI can produce it. A long report can be impressive and inconvenient. The right artifact fits the setting in which the reader will use it.

In a discussion about interviewing relatives, u/Silver_Co_Brooklyn described having a question list available:

“I have had an interview schedule prepared, meaning I had a list of questions printed out or available on my laptop screen (depending on the situation) that I could refer to keep the conversation on track and moving along.”

The commenter describes their own more formal oral-history work. That is a useful account of how a document can support an activity, not proof that every family interview needs the same format. Original comment.

In the same thread, u/theothermeisnothere wrote:

“Second, I bring some prepared questions but, more importantly, photos.”

Their account describes photographs prompting family stories. For an author designing a preparation skill, the implication is a question to investigate: should the plan include a place for meaningful objects or images the reader already has? It is not a reason to assume photographs will work for everyone. Original comment.

These two accounts also suggest a practical format constraint: the document should be easy to consult while listening, with room to depart from the prepared list.

Before drafting prompts, complete this table for the artifact you want.

The specification belongs to the author. AI can help draft it, but you decide whether it represents the method you want to teach.

The Oral History Association recommends preparing an open-ended guide and discussing the project's purpose and process with the narrator. Its guidance also addresses consent and the narrator's ability to decline subjects. Those principles inform this example; the short plan below is not a replacement for the association's full guidance. Oral History Association best practices.

Every factual field in the output needs a source. For a personalized plan, that source will often be the reader's answer. For a procedural instruction, it may be the author's reviewed method.

Create a small input-to-output map:

Ask only for information that changes the artifact. The skill does not need a complete family tree to help prepare a conversation about a childhood neighborhood.

If the reader provides sensitive details that do not help the task, avoid repeating them throughout the output. A useful document includes the information needed for its purpose, not every fact mentioned in the chat.

All names, details, and inputs in this example are fictional. The plan is written here as an expected artifact; it was not generated or tested in a live model session.

Reader inputs: Noor wants to speak with her uncle about the neighborhood where he grew up. They have discussed a short conversation, but the date and recording arrangements are not confirmed. Noor has a photograph of a street, without a reliable date. Her uncle prefers not to discuss a particular family disagreement.

Draft plan: childhood neighborhood conversation

Purpose: Learn what everyday life in the neighborhood was like from Uncle's perspective. This conversation is about his recollections; uncertain names and dates can remain uncertain.

Before the conversation: Confirm a convenient time and approximate length. Explain whether you hope to take notes or record, who would receive the material, and how he can ask to skip a question or stop. Do not start recording before agreement.

Materials: The street photograph, labeled “date unknown.” Do not present Noor's guess about its date as a fact.

Opening: “I'd like to hear what you remember about the neighborhood where you grew up. Is that still a topic you'd enjoy talking about today?”

Main questions:

1. What place in the neighborhood comes to mind first?
2. What would an ordinary day there look like for you?
3. Who did you spend time with, and what did you do together?
4. Is there a place or routine you miss, or remember differently now?

Optional follow-ups: “What happened next?” “How did you know that person?” “What do you remember seeing or hearing there?” Use these only when they fit what he has said.

Optional photo prompt: “Does anything in this photograph look familiar?” If it does not, set it aside. Do not pressure him to identify it.

Boundary: Do not pursue the family disagreement he asked to avoid. The plan does not need an explanation of why that topic is excluded.

Closing: Ask whether there is something important about the neighborhood that Noor did not ask. Confirm what, if anything, may be shared and whether he would like to review notes or a recording.

Afterward: Label the saved material with the actual conversation date and agreed topic. Keep uncertain details marked for possible later checking. Record the agreed sharing limits alongside it.

Still to confirm: Date, approximate length, recording or note-taking arrangements, and intended sharing.

A useful output can include a short rationale without becoming an essay. In this example, the questions focus on one place because the reader selected that topic. The photograph remains optional because neither its date nor its relevance is established. The excluded disagreement does not reappear as a probing follow-up.

Those links between input and output make the draft easier to check. The reader can say, “Actually, we want to discuss his first job,” and the skill can revise the focus rather than merely changing a heading.

Do not hide unresolved matters in a final footnote. Put them where the reader will act on them. Recording permission belongs in preparation, not after a list of instructions to record the conversation.

The deliverable remains a draft even when it is neatly formatted. Readiness depends on confirmed details and appropriate review, not visual polish.

Use a checklist tied to the method:

• Does every personalized detail come from the supplied inputs?
• Does each question serve the selected topic?
• Are uncertain facts visibly uncertain?
• Does the plan preserve the participant's stated boundaries?
• Can the reader find the next action quickly?
• Does it fit on a practical working page or need a shorter version?
• Is anything labeled complete that still requires agreement?

A failed check should lead to a specific revision. If the skill invents a photograph's date, remove the date and inspect why the instruction allowed guessing. If it generates twenty questions for a short conversation, reduce the scope rather than making the page smaller.

The guide to measuring agent skill quality expands on checking outputs against task criteria. Your author-specific checklist should remain the basis for judgment.

Copy the output into the format the reader expects to use. Can they print it, edit it, or consult it on their phone without losing the important distinctions? A chat response with many links and nested sections may be awkward as a working sheet.

Then test variants: a reader with no photographs, a different topic, unknown dates, and a request to cover too much. Check actual outputs against the same specification. Do not assume the successful illustrative plan proves those cases will work.

If you observe a real reader using the document, separate preparation quality from the later conversation's outcome. A usable plan does not guarantee a rich interview. Record what the artifact helped them do and what still required judgment.

Write one output specification and one completed example before building a broad companion. Include the unresolved version as well as the polished one so the skill has a model for honest incompleteness.

If you want to develop that process into an author skill, visit Skillfully and choose Book onboarding. Bring your book's method, the intended working document, and the checks you would use to judge it.