AI 驱动开发的七阶段 1. Grill 2. Research 3. Prototype 4. PRD 5. Issues 6. Implement 7. Review 来自 Skills For...
TL;DR · AI Summary
AI驱动开发的七阶段模型为软件开发流程提供了结构化框架，涵盖从问题对齐到代码审查的全过程。
Key Takeaways
- Grill阶段将模糊想法转化为共享理解，产出问题陈述和对齐文档。
- Prototype阶段使用可丢弃原型验证设计，减少开发风险。
- Review阶段通过人工QA发现问题并回环，确保代码质量。
Outline
Jump quickly between sections.
- §引言
介绍AI驱动开发的七阶段模型，强调其对软件开发流程的结构化作用。
将模糊想法转化为共享理解，产出问题陈述和对齐文档。
使用可丢弃原型验证设计/UX，降低开发风险。
描述终点而非路径，产出需求文档。
拆分任务为可并行执行的垂直切片，产出带依赖的工单DAG。
Agent执行开发任务，产出可运行代码。
通过人工QA发现问题并回环，确保代码质量。
Mindmap
See how the topics connect at a glance.
查看大纲文本（无障碍 / 无 JS 友好）
- AI驱动开发的七阶段
- Grill
- 问题陈述
- 对齐文档
- Prototype
- 可丢弃原型
- 验证设计
- Review
- 人工QA
- 发现问题
Highlights
Key sentences worth saving and sharing.
Grill阶段将模糊想法转化为共享理解，产出问题陈述和对齐文档。
Prototype阶段使用可丢弃原型验证设计/UX，减少开发风险。
Review阶段通过人工QA发现问题并回环，确保代码质量。
meng shao on X: "Seven Phases of AI-Driven Development 1. Grill 2. Research 3. Prototype 4. PRD 5. Issues 6. Implement 7. Review From Skills For Real Engineers by @mattpocockuk https://t.co/U8eABywlTP 7 phases: Purpose | Output 1. Grill: Turn fuzzy ideas into shared understanding | Problem statement + alignment 2. https://t.co/77Etprls9r" / X
meng shao
@shao__meng
Seven phases of AI-driven development 1. Grill 2. Research 3. Prototype 4. PRD 5. Issues 6. Implement 7. Review From Skills For Real Engineers author
@
github.com/mattpocock/ski…
7 phases: Purpose | Output 1. Grill: Turn fuzzy ideas into shared understanding | Problem statement + alignment 2.
research.md 3. Prototype: Validate design/UX with playable code | Disposable prototype 4. PRD: Describe the destination, not the path | Requirements document 5. Issues: Break into vertically sliced, parallelizable tasks | DAG of tickets with dependencies 6. Implement: Agent execution (TDD, Ralph, etc.) | Runnable code 7. Review: Manual QA, loop back if issues are found | QA plan + new tickets /grill-with-docs: This is an upgraded version of /grill-me, designed specifically for scenarios with a codebase Additional capabilities: 1. Domain language (CONTEXT.md) Ubiquitous language from DDD. CONTEXT.md is just a glossary, not a spec, not implementation notes. Example: "materialization cascade" is more token-efficient, searchable, and naming consistent than "lesson being real-ized in the filesystem with placeholders." 2. ADR (docs/adr/) Write only when all three conditions are met: irreversible, surprising without context, and real trade-off exists. 3. Four types of actions in a session · Challenge terminology against glossary · Stress-test boundaries with concrete scenarios · Identify contradictions against code · Make decisions immediately in CONTEXT, not batch them Division of labor between /grill-with-docs and /grill-me: With a codebase → /grill-with-docs; Without a codebase (writing obituaries, pure product ideation) → /grill-me.
Matt Pocock
@mattpocockuk
20h
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
Show more
12:24 AM · Jun 16, 2026
4.2K
Views
1
2
12
4
8
48
5
7
57