From User Stories to AI Prompts: A Framework You Already Know

I have never worked in IT. But I have spent the better part of my career right next to it.

That proximity gave me an early crash course in Agile, and specifically in writing user stories. For anyone unfamiliar, a user story is a simple framework used in software development to capture what a person needs and why. It sounds like this:

As a tired but determined person, I want a realistic, low-stress plan for the next 3 hours so that I can be productive without feeling overwhelmed.

The goal is to build something that genuinely meets the needs of the person using it. You are not describing the solution. You are describing the need, and the "why" behind it. Compile enough of these and a product starts to take shape.

I will be honest. When I first learned this, I thought it was a little ridiculous. Saying "I am this person and I want this thing" felt clunky and almost childlike. It took practice to see what the structure was actually doing.

Flash forward to today. I have been going deep on AI prompting, working to move beyond basic one-liners toward something more intentional and repeatable. And somewhere in that process, I hit a familiar feeling.

I had done this before.

The RCRQ method, which stands for Role, Context, Request, and Question, maps almost perfectly onto the user story framework I had learned years earlier. Here is what that looks like in practice:

Role: You are a witty life coach with a sense of humor. Context: I have had a busy day and limited energy, but a strong desire to be productive without being miserable. Request: Help me plan my next 3 hours in a way that feels doable but not hectic. Question: Ask me what is on my list and what kind of reward would motivate me.

Where they overlap

Both frameworks ask you to define who is involved, describe the situation, and articulate the need. That parallel is not a coincidence. Good user stories and good prompts are solving the same fundamental problem: how do you communicate a human need clearly enough that something else, whether a development team or an AI model, can actually solve it?

The "who" works differently in each. In a user story, you are defining who the solution is being built for. In a prompt, you are telling AI whose perspective to adopt when building it. That shift changed how I approach prompting entirely. When I tell an AI to respond as a witty life coach rather than just asking for a productivity plan, the output is sharper and more useful.

Context in a prompt does something a user story's "so that" clause only partially achieves. It adds humanity. It tells the story behind the need, not just the need itself.

The biggest difference is what happens at the end. A user story stops short of prescribing the solution. The development team figures that out. A prompt just asks. And then it can keep asking, iterating, refining, in real time. What might take weeks of requirements gathering and sprint planning can be roughed out in a single conversation.

Why this matters right now

AI is increasingly being used to write user stories themselves. The circle is closing. But whether you are writing a user story for a development team or a prompt for an AI model, the underlying skill is the same: the ability to define a need clearly, give it context, and ask the right questions.

That turns out to be a very human skill. And one worth developing intentionally.

What frameworks from your own work have you found yourself applying in unexpected places? I would love to know what is clicking for others.