Jonah Martin (@jonahmartin)

Forked from@imaniokafor/The checklist I use for getting an agent to stop safely

The checklist I use for getting an agent to stop safely

The first answers were broad enough to be useless. This version asks for assumptions, evidence, and a next step.

Jonah Martin

I am stuck on getting an agent to stop safely. I need to define approval gates and stop conditions before an agent changes data or sends anything, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

First, shrink the decision. Do not solve the whole subject at once. 1. Put the source of truth in the prompt. 2. Mark missing evidence instead of filling it in. 3. Add a stop condition before tool use. 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

3200

Jonah Martin@jonahmartin·2w ago

Forked from@jasperwong/A practice-first plan for writing eval cases before changing a prompt

A practice-first plan for writing eval cases before changing a prompt

I asked for a plan built around attempts and feedback, not a list of resources.

Jonah Martin

I want to learn writing eval cases before changing a prompt, 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 writing eval cases before changing a prompt 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

Jonah Martin@jonahmartin·2w ago

Forked from@quinnharper/A practice-first plan for reading uncertainty in a dashboard

A practice-first plan for reading uncertainty in a dashboard

I asked for a plan built around attempts and feedback, not a list of resources.

Jonah Martin

I want to learn reading uncertainty in a dashboard, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain reading uncertainty in a dashboard 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

Jonah Martin@jonahmartin·4w ago

The checklist I use for a prompt for honest product feedback

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

Jonah Martin

I am stuck on a prompt for honest product feedback. I need to review a product idea without defaulting to praise or inventing market evidence, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

Show all 3 messages

3412.4k

Jonah Martin@jonahmartin·1mo ago

a prompt for honest product feedback: the version with actual constraints

This started as a messy question about a prompt for honest product feedback. The follow-up made the answer practical.

Jonah Martin

Give me a short checklist for a prompt for honest product feedback. I want something I can run before I call the work done.

Claudeclaude-opus-4.5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Put the source of truth in the prompt - [ ] Mark missing evidence instead of filling it in - [ ] Add a stop condition before tool use - [ ] 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

3311.2k

Jonah Martin@jonahmartin·2mo ago

I asked Gemini for a second opinion on a prompt for honest product feedback

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

Jonah Martin

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

Geminigemini-2.5-pro

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, mark missing evidence instead of filling it in.

Show all 3 messages

3312.7k

Jonah Martin@jonahmartin·3mo ago

The a prompt for honest product feedback prompt I actually kept

This started as a messy question about a prompt for honest product feedback. The follow-up made the answer practical.

Jonah Martin

Help me review a product idea without defaulting to praise or inventing market evidence. 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 your recommendation.

ChatGPTgpt-5

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 prompt for honest product feedback, I would start with these checks: - Put the source of truth in the prompt - Mark missing evidence instead of filling it in - Add a stop condition before tool use If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

331987

Jonah Martin@jonahmartin·3mo ago

A smaller way to tackle a prompt for honest product feedback

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

Jonah Martin

For a prompt for honest product feedback, 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 a prompt for honest product feedback, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3414k

Public pits

The checklist I use for getting an agent to stop safely

A practice-first plan for writing eval cases before changing a prompt

A practice-first plan for reading uncertainty in a dashboard

The checklist I use for a prompt for honest product feedback

a prompt for honest product feedback: the version with actual constraints

I asked Gemini for a second opinion on a prompt for honest product feedback

The a prompt for honest product feedback prompt I actually kept

A smaller way to tackle a prompt for honest product feedback