The Ladder of Logical Progression (Step-by-Step Thinking)

Make each stage its own tag - <setup>, <working>, <answer>, <independent_check> - so the structure is in the prompt rather than in a paragraph describing a structure. Claude responds well to being asked to show its reasoning before its conclusion, and better still to a <provenance> stage marking which claims came from your facts, which from general patterns and which from its own assumptions. That last block is what tells you how much of an analysis would survive being wrong.

• One tag per stage; the tags are the structure.
• Add a <provenance> block separating your facts from its assumptions.
• Ask for an independent check, not a restatement.
• Say what to do when a stage cannot honestly be completed.
• Ask for a position, not a balanced summary.

<problem>
A train leaves Hyderabad at 3 PM travelling at 60 km/h. A car leaves Hyderabad at 3:30 PM on the same route travelling at 80 km/h. At what time will the car overtake the train?
</problem>

<task>
Solve it. I am not asking you to think step by step - you do that anyway. I am asking for the working in a checkable shape, and for a second route to the same answer.

Structure your response in these blocks:

<setup>
State what is known and what is being asked, in your own words. If anything in the problem is ambiguous - whether 60 km/h is an average including stops, whether "same route" means identical distance - say so here before solving.
</setup>

<working>
A table: Quantity, Value, Unit, Derivation. Rows for the head start distance, the relative speed, the time to close the gap, and the overtake time. The Derivation cell names the arithmetic performed.
</working>

<answer>
One line.
</answer>

<independent_check>
Verify by a different route: compute the distance each vehicle has travelled at the time you found, working forward from each vehicle's own departure, and confirm the two distances are equal. Do not reuse the relative-speed figure here - that would check the arithmetic against itself. If the two distances disagree, say the answer is wrong and stop.
</independent_check>

<where_this_goes_wrong>
The step a student most commonly gets wrong on problems of this shape, and what the wrong answer looks like.
</where_this_goes_wrong>
</task>

<context>
I own a successful biryani house in Kondapur, Hyderabad. I am considering opening a second branch in Begumpet. I want a consultant's analysis, not encouragement.
</context>

<task>
Work through this in labelled stages. The staging is so that I can disagree with one stage without discarding the whole analysis.

<stage_1_missing_information>
What you would need to know before a recommendation is worth anything: revenue and margin, how much of the Kondapur outlet's success depends on my personal presence, kitchen capacity, staff depth, capital available. Ask rather than assume.

If the gaps are large enough that stages 2 to 5 would be guesswork dressed as analysis, say so plainly here and let me fill them in first. I would rather be sent away for a week with homework than handed a confident analysis of a business you know nothing about.
</stage_1_missing_information>

<stage_2_case_for>
At least three benefits, specific to Begumpet and to biryani rather than to expansion in general.
</stage_2_case_for>

<stage_3_case_against>
At least three risks. Include the ones independent restaurant owners typically underestimate: founder attention splitting across two kitchens, quality drift, cannibalisation, the real carrying cost of a second lease before it breaks even.
</stage_3_case_against>

<stage_4_market>
Begumpet against Kondapur: residential and office mix, competition, footfall timing.
</stage_4_market>

<stage_5_recommendation>
Take a position. Not a balanced summary - a position, with the reasoning that got you there. Then the single most important thing I should establish before deciding, and how to establish it within thirty days.
</stage_5_recommendation>

<provenance>
Go back through stages 2 to 5 and mark which claims came from what I told you, which from general industry patterns, and which from assumptions you made. I want to know which parts of this analysis would survive you being wrong about Hyderabad.
</provenance>
</task>

<context>
I want to launch a podcast about the history of Indian startups. I have not started. I need the whole path, structured so I do not do things in the wrong order.
</context>

<task>
Build the plan as phases with decision gates between them, not as a flat checklist. A flat checklist lets me buy a microphone before I have decided who the show is for, which is the standard way this goes wrong.

For each of the three phases: the steps in order, then a <gate> naming the one question that must be answered before the next phase begins.

<phase_1>Pre-production: niche and audience; name and branding; format and episode length; equipment at entry, mid and serious tiers with rupee ranges; hosting platform.</phase_1>
<phase_2>Production and post-production: guest sourcing and outreach; recording setup including remote guests; editing workflow; show notes and transcripts; cadence and how many episodes to bank before launch.</phase_2>
<phase_3>Launch and marketing: directory submissions; launch sequence; distribution and clips; promotion across the first ten episodes; what to measure and what to ignore.</phase_3>

Then, outside the phases:

<out_of_order>The steps people most commonly do too early, and what it costs them.</out_of_order>
<india_specific>Anything specific to launching from India: hosting payment, guest availability and outreach norms, which platforms Indian listeners actually use, language mix.</india_specific>
<unskippable>The two or three steps that genuinely cannot be skipped, separated from the ones that merely feel urgent. Be willing to tell me most of this list is optional if it is.</unskippable>

Put the phased plan in an Artifact so I can work against it over weeks and edit it as things change. Keep your commentary on sequencing in the chat.
</task>