Test it, trim it, hand it on
Build-along · ~30 min at your own keyboard
A folder is finished when someone else can use it. Run four checks. First, open a fresh session with only the folder and ask it to do the job. Whatever it gets wrong is missing from the folder. Second, find each fact that appears in two places and keep one. Duplicates drift apart. Third, add a last-checked date and write what triggers an update, such as a price change. Fourth, give the folder to one other person and have them try it. Write down where they got stuck. Their confusion is your list of what to fix.
Ladder · Level 6The long version: Workflows ↗
Do this
0/6Checkpoints
- ▸You should now see a list of what the fresh session got wrong, and what you added.
- ▸You should now see each key fact in one place only.
- ▸You should now see a last checked date, two update triggers, and notes from one other person.
The three ways this goes wrong
- You ran the test in a chat that already knew your work. — Use a new chat or project that sees only the folder. Otherwise the test proves nothing.
- Your handoff person asked you questions the whole time. — Write each question down. Each one is a gap in the folder. Put the answer in the map file.
- You found no duplicates and moved on. — Search five specific facts and list them. If a price or a rule appears twice, you have a duplicate.
Share what happened
Paste your four results. The fresh test, the duplicates you removed, your last checked line with its triggers, and what your other person could not follow.
Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].
🔒 Don't paste confidential, personal-health, or payment info.