Caleb Bose (@calebbose)

Forked from@mirakhan/A smaller way to tackle agent handoff notes

A smaller way to tackle agent handoff notes

I wanted help with agent handoff notes without pretending the model knew facts I had not provided.

Caleb Bose

For agent handoff notes, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

ChatGPTgpt-5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For agent handoff notes, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3200

Caleb Bose@calebbose·2w ago

Forked from@kenjifujita/I finally found a good way to learn using property-based tests

I finally found a good way to learn using property-based tests

The useful change was doing a small retrieval check before reading more.

Caleb Bose

I want to learn using property-based tests, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Claudeclaude-opus-4.5

Good. Do these without looking anything up: 1. Explain using property-based tests in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6100

Caleb Bose@calebbose·3w ago

A blunt review of my approach to a competitor brief

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Caleb Bose

Give me a short checklist for a competitor brief. I want something I can run before I call the work done.

ChatGPTgpt-5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Start from observed behavior - [ ] Write the riskiest assumption down - [ ] Choose a measurable next test - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

330849

Caleb Bose@calebbose·1mo ago

How I ask for help with a competitor brief

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Caleb Bose

Be blunt about my plan for a competitor brief. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Claudeclaude-opus-4.5

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, write the riskiest assumption down.

Show all 3 messages

3302.3k

Caleb Bose@calebbose·2mo ago

What finally made a competitor brief click for me

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Caleb Bose

Help me compare competitors by customer, workflow, pricing, and evidence without copying marketing claims. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change you

Geminigemini-2.5-pro

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a competitor brief, I would start with these checks: - Start from observed behavior - Write the riskiest assumption down - Choose a measurable next test If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3303.7k

Caleb Bose@calebbose·3mo ago

Gemini found the hole in my a competitor brief plan

This started as a messy question about a competitor brief. The follow-up made the answer practical.

Caleb Bose

For a competitor brief, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

Geminigemini-2.5-pro

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For a competitor brief, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3403.7k

Caleb Bose@calebbose·3mo ago

My notes from fixing a competitor brief

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Caleb Bose

I am stuck on a competitor brief. I need to compare competitors by customer, workflow, pricing, and evidence without copying marketing claims, but my current attempt is getting vague and too big. What would you check first?

ChatGPTgpt-5

First, shrink the decision. Do not solve the whole subject at once. 1. Start from observed behavior. 2. Write the riskiest assumption down. 3. Choose a measurable next test. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

340906

Public pits

A smaller way to tackle agent handoff notes

I finally found a good way to learn using property-based tests

A blunt review of my approach to a competitor brief

How I ask for help with a competitor brief

What finally made a competitor brief click for me

Gemini found the hole in my a competitor brief plan

My notes from fixing a competitor brief