Aya Lin (@ayalin)

Forked from@jonahmartin/The a prompt for honest product feedback prompt I actually kept

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.

Aya Lin

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

3200

Aya Lin@ayalin·2w ago

Forked from@oscarlind/What I was getting wrong about tool approval gates for AI agents

What I was getting wrong about tool approval gates for AI agents

Sharing the correction because the mistake looked reasonable until I tested it.

Aya Lin

I want to learn tool approval gates for AI agents, 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 tool approval gates for AI agents 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

Aya Lin@ayalin·2w ago

Forked from@idrisbello/What I was getting wrong about writing a metric contract

What I was getting wrong about writing a metric contract

Sharing the correction because the mistake looked reasonable until I tested it.

Aya Lin

I want to learn writing a metric contract, 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 writing a metric contract 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

Aya Lin@ayalin·3w ago

The question that cleaned up database migration rehearsal

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Aya Lin

Help me turn a risky schema change into staged, measurable deployment steps. 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. Otherwise, s

Claudeclaude-opus-4.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 database migration rehearsal, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3403.3k

Aya Lin@ayalin·1mo ago

I stopped guessing about database migration rehearsal

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

Aya Lin

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

Claudeclaude-opus-4.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 database migration rehearsal, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

330214

Aya Lin@ayalin·2mo ago

I needed a usable answer on database migration rehearsal

Not magic wording, just enough context and a clear definition of done. Easy to adapt.

Aya Lin

I am stuck on database migration rehearsal. I need to turn a risky schema change into staged, measurable deployment steps, but my current attempt is getting vague and too big. What would you check first?

Geminigemini-2.5-pro

First, shrink the decision. Do not solve the whole subject at once. 1. Reproduce the failure before changing code. 2. Keep the patch smaller than the diagnosis. 3. Write the rollback before deployment. 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

3303.2k

Aya Lin@ayalin·2mo ago

database migration rehearsal, minus the vague advice

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

Aya Lin

Give me a short checklist for database migration rehearsal. I want something I can run before I call the work done.

Geminigemini-2.5-pro

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Reproduce the failure before changing code - [ ] Keep the patch smaller than the diagnosis - [ ] Write the rollback before deployment - [ ] 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

3403k

Aya Lin@ayalin·3mo ago

ChatGPT was overcomplicating database migration rehearsal, so I reset the question

I wanted help with database migration rehearsal without pretending the model knew facts I had not provided.

Aya Lin

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

ChatGPTgpt-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, keep the patch smaller than the diagnosis.

Show all 3 messages

3401.8k

Public pits

The a prompt for honest product feedback prompt I actually kept

What I was getting wrong about tool approval gates for AI agents

What I was getting wrong about writing a metric contract

The question that cleaned up database migration rehearsal

I stopped guessing about database migration rehearsal

I needed a usable answer on database migration rehearsal

database migration rehearsal, minus the vague advice

ChatGPT was overcomplicating database migration rehearsal, so I reset the question