@mattpocockuk: Here are my 7 phases of AI-powered development. I've been thinking that the pre-PRD phase needs more structure. You nee…
Summary
Matt Pocock shares his seven phases of AI-powered development, emphasizing the need for more structure in the pre-PRD phase.
View Cached Full Text
Cached at: 06/15/26, 10:58 AM
Here are my 7 phases of AI-powered development.
I’ve been thinking that the pre-PRD phase needs more structure. You need to figure out the shape of the design tree first, before then walking down it with higher-fidelity prototypes.
In other words, /grill-with-docs needs to https://t.co/Pw9kL6bDDr
Similar Articles
@shao__meng: Seven Stages of AI-Driven Development 1. Grill 2. Research 3. Prototype 4. PRD 5. Issues 6. Implement 7. Review From Skills For Real Engineers by @…
A Twitter thread shares the seven stages of AI-driven development from the Skills For Real Engineers project by @mattpocockuk, including alignment techniques like grill sessions and tooling for coding agents.
@mattpocockuk: The 3 main 'prep' activities in software development are: - Discuss: figure out what to build - Research: summarize wor…
A developer outlines three main prep activities in software development (discuss, research, prototype) and asks why AI's usefulness in these wasn't obvious sooner.
@vikingmute: Great workflow, now it's also my main workflow for developing new features and new ideas: Grill - let AI fiercely question every detail until clear -> Research - separately analyze difficult areas and create a research document (optional) -> PRD - gen...
VikingMute shares their main workflow for developing new features and ideas: using AI (Grill) to drill down on details, Research to analyze difficulties, generating a PRD, breaking it into independent Issues, step-by-step implementation, and finally Review. This is a supplement to Matt Pocock's seven-stage AI development method.
@mattpocockuk: Alper is right, setting expectations on software quality early is really key I.e. explicitly calling what you're buildi…
This tweet highlights the importance of setting clear expectations on software quality early, such as calling projects prototypes, to improve interactions with AI agents and prevent unnecessary overengineering.
@mattpocockuk: Do you feel in control when you're coding with AI? Can you: - Get it to build the thing you wanted? - Stop it making th…
A promotional tweet for a new course aimed at helping developers achieve better control and efficiency when coding with AI, addressing issues like accuracy and task management.