SiSu RevOps

M4  /  L4.2  /  about 13 minutes

The folder changes the plan

You now have a brief, the one you wrote yourself in Lesson 1. It sits in 20-briefs/, and it works.

Then a colleague copies it into their own workspace, or you open a session with the folder not quite set up. The output comes back close, not the same, and it differs in ways you would not expect.

This lesson is about where instructions live and what happens when a layer is missing. It is the last time this will surprise you.

What you will be able to do

  • Sort your rules between global instructions, the folder file, and the brief.
  • Recognise the failure shape of a missing context layer.
  • Say honestly what this course can and cannot tell you about packaging a brief for others.

The folder changes the plan, not just the wording

Per-folder context files carry the project rules. At session start Claude reads MEMORY.md for cross-project learnings and, inside a project folder, that folder's own CLAUDE.md and MEMORY.md.

The part people underestimate: the folder file does not decorate the output, it changes the plan. If CLAUDE.md says renewal amounts must never be added to new business amounts, the plan for "total this account" is a different plan, not the same plan with a nicer label. Remove the file and you get different work, not the same work presented differently.

This is why Module 2 came before Module 4: rails are built once and inherited, and this is where you find out what you inherited. Try naming one rule in your own CLAUDE.md whose removal would change a number, not a format.

Three places a rule can live

Three layers now, not two. Sorting a rule into the wrong one is the most common configuration mistake in this course, and each mistake has its own smell.

Layer What belongs there The smell when a rule is in the wrong layer
Global instructions Who you are, how you write. True in every session you ever run. A global rule that refers to a folder is wrong most of the time, so you quietly delete it, and then it is missing from the sessions where it mattered.
Folder CLAUDE.md What this body of work is. Facts about this data, output conventions, standing safety rails, the exceptions rule. A folder rule that only applies to one workflow makes every other workflow in the folder behave oddly.
Brief file What this run does. Outcome, inputs, output shape, definition of done, stopping condition. A brief that restates the folder rules is a brief nobody maintains, and the copies drift.

The test, applied in order:

  1. Would this be true in a session about my personal calendar? Then it is global.
  2. Would this be true for every task in this folder? Then it is folder.
  3. Otherwise it is brief.

Worked on real rules from earlier modules:

  • "Write plainly, no marketing adjectives": global.
  • "opportunities.amount is in local billing currency; accounts.arr_usd is USD": folder. A fact about this data, true for every task that touches it.
  • "Sections in this order: account facts, opportunity history, contacts, activities, reconciliation": brief. Only this workflow has those sections.
  • "Anything unresolvable goes to exceptions.csv and do not guess": folder, wanted on every task. Lesson 3 shows why it is the highest-yield line in the course.

Now sort your own: which rules in your brief should move down to the folder?

Where reusable work lives, and what we will not teach you

The brief you wrote in Lesson 1 is worth more than the output it produced. The output answers one question about one account. The brief answers it every quarter, for any account, for anyone who has the file. So: 20-briefs/<workflow>.brief.md, in version control if you have any, named after the workflow, not the day.

Now the honest part. Cowork supports skills, domain expertise that activates automatically, and plugins, which package skills, MCP connectors, subagents, slash commands and hooks. So packaging a mature brief as an installable skill or plugin is possible, and it is the natural next step when a team wants to use your workflow rather than copy your file.

But this course's verified facts do not include the authoring format for a skill file. So we teach the file route, which we can teach accurately, and name the packaging route as one to explore with current documentation, without inventing a format.

That models the standard to hold on your own outputs: say what you know, name what you do not, never fill the gap with something plausible. If you take one habit into work where nobody is grading you, take that one.

The experiment: one layer removed

The same brief, run twice. Worth doing, not just reading.

Run A: everything in place. revenue-workspace/CLAUDE.md (the folder file you wrote in Module 2) present, brief file present. The request: Run the brief in 20-briefs/account-snapshot.brief.md for account ACC-02848. Output: the six sections in order, money as 55,000 USD, dates as 2025-10-19, a Reconciliation section reading four rows and three distinct opportunity ids, one row in exceptions.csv, and a first line naming the source files.

Run B: CLAUDE.md moved out of the folder. Same brief file, same request, same data. I changed nothing in the brief: otherwise I would not know which layer made the difference.

The brief still carried the output shape, so the sections were right. Missing was everything the brief relied on the folder for: the source-files line, the output location convention, the standing exceptions rule. The reconciliation survived, because it lives in the brief's definition of done. The exceptions file was thinner, because "do not guess" lived in the folder file.

The output did not fall over. It got quietly less defensible, and nothing announced it. There is no error message for "your configuration was less complete than usual".

Try this now

  1. Open a fresh session. Temporarily move revenue-workspace/CLAUDE.md out of the folder. Rename it, do not delete it.
  2. Ask the way a busy person asks on a Tuesday, without naming the brief file. That is what gets typed when you are in a hurry and believe the setup remembers you.
Same account snapshot as before, for ACC-02848.
  1. Restore CLAUDE.md, open another fresh session, and run Run the brief in 20-briefs/account-snapshot.brief.md for account ACC-02848. Compare the two outputs side by side.

What you should see: two failures stacked, and separating them is the exercise.

Failure one: "as before" refers to nothing. There is no memory between sessions, so "before" is not something the session can resolve. What you get depends on what is lying around: if a previous snapshot sits in 30-output/, the run may find it and imitate its shape. That looks like memory and is not.

Failure two: the missing layer is invisible in the output. Different section order, a different sort, money without currency codes, no exceptions file. Each difference is small. Together they produce a document close enough that a busy person pastes it into a deck.

The thing to look for on this account: whether the run silently picked one of the two OPP-007099 rows. The stopping condition that forbids picking lives in the brief, so naming the brief keeps it. Saying "as before" never loads it.

Worth knowing: the guard is two files doing different jobs. The brief file, named in the request, carries what this run does. The folder context file, read at session start, carries what this folder always does. Plus one habit: never ask for "the same as before". Name the brief. Eight words, and the difference between a reproducible run and a run that inherited whatever was on disk.

Write down, in one sentence, which difference between your two outputs would have been costliest unnoticed. That sentence goes in your run log in Lesson 4.

What you keep

  • revenue-workspace/CLAUDE.md, updated with any rule from your brief that belonged one layer down.
  • 20-briefs/account-snapshot.brief.md, unchanged, plus a note at the bottom recording which folder rules it depends on: what the next person must bring when they copy the file.
  • Both outputs from the experiment, kept side by side until Lesson 4.

Check yourself

  1. Sort these into global, folder or brief: (a) "Our fiscal year equals the calendar year"; (b) "Output goes to 30-output/<workflow>/"; (c) "Sort the opportunity history oldest first"; (d) "Never write to a file in 10-data/"; (e) "I prefer short sentences".
  2. A colleague copies your brief file into their own workspace and gets differently shaped output. Name the two most likely causes, which one you would check first, and how.
  3. Someone says they have packaged their brief as a skill so their team can install it. What one question would you ask, and what would you not assert about the format?
  4. Your run produced a snapshot that looks like last quarter's, and you did not name the brief file. Give two explanations consistent with there being no memory between sessions, and what you would look at to tell them apart.
Answers

1, one line per option:

  • (a) Fiscal year: folder. A fact about this body of work, wrong or irrelevant anywhere else.
  • (b) Output path: folder. It names a path that only exists inside this workspace, which is exactly what makes it a bad global rule.
  • (c) Sort oldest first: brief. Only this workflow has an opportunity history to sort.
  • (d) Never write to 10-data/: folder. A standing safety rail for every task in the workspace.
  • (e) Short sentences: global. How you write, true in every session.

2. Either they do not have your folder CLAUDE.md, or theirs differs. Check the first, because it is one look: if their output lacks the Source files: line and the 30-output/ path, the folder layer is absent rather than different. This is why your brief carries a note listing the folder rules it depends on.

3. Ask which current documentation they used for the format, and assert nothing about it yourself. This course documents that skills and plugins exist and what they package, not how a skill file is written.

4. Either the run read last quarter's output from the granted folder and imitated it, or it produced a generic default that resembles it. Neither is memory. Move last quarter's output out of the granted tree and re-run: if the resemblance disappears, it was reading the file.

Where this goes next

Next lesson: evidence that proves an output right at a cost below the work, and the one instruction that turns unresolvable rows from invisible guesses into a list you can read.

Track labs: the exercise sheet in labs/LAB-04 of your practice pack (start with its README). Part A runs this experiment as a required step and asks you to diff the two outputs and name the costliest difference.