Start from a product vision board
Fill in one page with five boxes before you plan anything. Who is it for? Which pains, needs and wishes do they have? Which product and features answer that? What are your business goals, and how do you measure them? What is your vision statement, in one sentence? When you doubt what to do next, this page decides.
Find your words with a messaging canvas
A messaging canvas gives you the words for your product. It asks what struggle your customer has, which job your solution does, why people hesitate, how aware they are of the problem, what makes you different and what their life looks like afterwards. With those answers you design with real content from the first wireframe, and you never fill a layout with lorem ipsum.
Fill your backlog with user stories
A user story says who wants what and why: “As a student, I want to check in with one tap, so that I never lose my 70%.” Add acceptance criteria in Given, When, Then form, so you know how to demo the story. Many teams plan with features, and that works. I like stories because they start from the need, so the solution stays open until you design it.
Keep the backlog short, ordered and estimated
One person orders it by value, with the most valuable story on top. Estimate with points (1, 2, 3, 5, 8, 13, 20) or with T-shirt sizes: S, M, L and XL. A burn-down chart is handy for a team, but when you work alone, or with an AI agent that builds fast, it is mostly overhead. Keep about 20 stories and detail only the top few. A story is ready when it fits in one sprint.
Do research, design and build in the same sprint
A waterfall researches first, designs second and builds last, and you see a result at the end. In a sprint you do a little of everything. Talk to a user, sketch a wireframe, build the screen and show it, then go around again. Start with the content, move to wireframes, then build a clickable prototype, and improve the features each round with what you learned.
Finish every sprint with a working product increment
Plan on a board with four columns: Backlog, In this sprint, Doing and Done. Pick the stories you can finish, write one sprint goal and keep one story in Doing at a time. When the sprint ends, something works and a real person can try it. Your vision decides what that increment is, so ask yourself what the end goal of your sprints is.
End each sprint with a short retro
Ask three questions: what went well, what could be better, and what are the top three things to take along into the next sprint? Another format is the hero’s journey. What did I do as the hero, who or what was my guide, what treasure did I find, and which cavern got in my way? Put the three things on the backlog of the next sprint, so they happen.
Alone, you wear every hat
You are the strategist, the designer, the developer, the product manager, the researcher and your own product owner. The last one is the hard one, because you own your own thing. Ask a sprint buddy to join the review and the retro. They see what you cannot see.
Let your agent sprint with you
With an AI agent, the story is the prompt and the acceptance criteria are the test. Keep the backlog as a file in your project and write your working rules in an AGENTS.md. Building is the fast part now, so your own review is the bottleneck. The six sprint skills below handle the routine. Install them and type /sprint-session, the orchestrator that calls the other skills, and you get a vision board, user stories and a messaging canvas in one go. Type /sprint-planning to plan and run the sprint itself.

