L1Lesson 4Free

Choose the output shape

Summary, checklist, rewrite, or memo

After this, you'll be able to create a file-output brief and use it to make Claude's work with local files safer and easier to verify.

Before you start

Complete Separate private and irrelevant files first.

The idea

Files are input. The output still needs a shape, audience, and check. This lesson asks you to make a file-output brief, not a broad promise that Claude can use files. The output should be specific enough that you can inspect what Claude read, what it produced, and what still needs review.

Summary, rewrite, table, packet, and question-list outputs compete before the task is clear.

Here is the before and after: Before, Claude summarizes whatever catches its attention. After, it reads the same files for a purpose: client summary, checklist, rewrite, decision memo, comparison, or handoff packet. For example, a client folder might include notes, drafts, exports, and old versions. The lesson output should say which files are in scope, which are out, what Claude is making, and how you will prove the result came from the right source.

Now try it: Choose one output shape before asking Claude to read deeply. Make one choice before asking Claude to work: folder, file set, output shape, source check, access path, or maintenance rule. That choice keeps desktop file work from becoming vague local search.

Choose the output shape runtime mapThe folder workflow works when a file-output brief connects the input, the check, and the next step.

Messy inputThe raw desktop files material before the lesson shapes it.
a file-output briefThe thing you can inspect, edit, and reuse.
Review checkThe source check that catches a weak assumption.
Next stepThe output moves into the next lesson instead of sitting alone.

The lesson is done when you can show the source boundary, the output, and the check that proves the output is safe to use.

Try it (15 min)

Watch out for

Asking for several outputs at once.
Letting Claude fill gaps from assumption instead of questions.
Forgetting to name the audience.

Paste this into Claude

Using the approved source files, help me choose one output shape: summary, checklist, rewrite, decision memo, comparison, or handoff packet. Audience: [who will use it]. Include why this shape fits, what sources matter, and how we will check it.

If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic File Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Trust This Without Fixing It. Keep the answer practical enough that I can paste it into my folder workflow notes.

What a good response looks like

Finished Artifact:
- a file-output brief
- Why it matters: it gives the folder workflow a concrete thing to inspect instead of a vague intention.
- Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything.

Reality Check:
- The artifact names the user, input, decision, owner, or proof it depends on.
- The weakest assumption is visible.
- The next step can be completed in one sitting.

What good looks like

One output shape is selected.
The audience is named.
Source files are tied to the shape.
A review check is included.

Go deeper (8 min)

Paste this into Claude

Without rereading the lesson, explain why a file-output brief matters in three bullets. Then apply it to a second file example: [describe a different folder or document set]. Return What Changed, What Stayed The Same, What To Check Before Trusting The Output, and the exact next action.

What a good response looks like

Transfer Check:
- What changed: the second example has a different audience, input, or delivery context.
- What stayed the same: a file-output brief still needs a source, a review check, and a next step.
- Before trusting it: inspect the source check that would catch a wrong assumption.
- Next action: run the check once, then carry the revised artifact into the next lesson.

What good looks like

You explained the lesson idea from memory before applying it again.
The second example changes the artifact instead of copying the first answer.
The trust check names a real risk.
The next action can be done in one sitting.

When this breaks

Fails when the output shape is vague because the result becomes a generic summary.
Breaks when the audience is missing because the file work has no useful level of detail.

AI can help with this

Paste the exercise prompt into Claude with your real folder or file context. Ask Claude to interview you one question at a time, produce a file-output brief, challenge the weakest assumption, and rewrite the artifact once so it is ready for the next file step.

One output shape is chosen and the file path points toward that shape.

You can now

You can point to a file-output brief.

You can explain which files are in scope.
You can name the assumption that still needs checking.
You can use the output in the next lesson.

Key takeaways

The folder gives Claude material. The output brief tells it what to make from that material.

Pick one output shape per run.
Name the audience.
Tie files to the output.
Turn uncertainty into questions.

Was this helpful?

Up nextTurn files into a sourced summary

Separate private and irrelevant files Turn files into a sourced summary

← Back to Claude Cowork

Using the approved source files, help me choose one output shape: summary, checklist, rewrite, decision memo, comparison, or handoff packet. Audience: [who will use it]. Include why this shape fits, what sources matter, and how we will check it. If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic File Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Trust This Without Fixing It. Keep the answer practical enough that I can paste it into my folder workflow notes.

Finished Artifact: - a file-output brief - Why it matters: it gives the folder workflow a concrete thing to inspect instead of a vague intention. - Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything. Reality Check: - The artifact names the user, input, decision, owner, or proof it depends on. - The weakest assumption is visible. - The next step can be completed in one sitting.

Without rereading the lesson, explain why a file-output brief matters in three bullets. Then apply it to a second file example: [describe a different folder or document set]. Return What Changed, What Stayed The Same, What To Check Before Trusting The Output, and the exact next action.

Transfer Check: - What changed: the second example has a different audience, input, or delivery context. - What stayed the same: a file-output brief still needs a source, a review check, and a next step. - Before trusting it: inspect the source check that would catch a wrong assumption. - Next action: run the check once, then carry the revised artifact into the next lesson.