Objective
Your mission
Take a project bigger than a single-session build, break it into MVP-first chunks, sequence them, and build chunk 1. Output: chunking_plan.md.
You need: Any AI coding tool. A text editor.
Time: 30-40 minutes.
Step 1: list the full feature set (5 min)
Take a project idea you have — something bigger than what you'd build in one sitting. List every feature you eventually want.
Write in your file:
## Project: [name]
### Full Feature List
1. [feature 1]
2. [feature 2]
3. [feature 3]
...
Step 2: break it into MVP-first chunks (10 min)
Instead of building everything at once, build the smallest version that works, then add features one at a time.
Example — Project Management App:
- Chunk 1 (MVP): Create a project (name only). See list of projects. Delete a project. localStorage. No tasks, no teams, no dashboard.
- Chunk 2: Add tasks to a project. Task has name and status (todo, done).
- Chunk 3: Add task assignment. Show tasks grouped by assignee.
- Chunk 4: Add comments on tasks.
- Chunk 5: Add simple dashboard — count of projects, total tasks, completed tasks.
Each chunk is a complete, testable build. You ship chunk 1, test it, then add chunk 2.
Write in your file:
## Chunking Plan
### Chunk 1 (MVP): [describe in 2-3 sentences]
### Chunk 2: [describe in 2-3 sentences]
### Chunk 3: [describe in 2-3 sentences]
...
The chunking rule
If you can't describe a feature in 2-3 sentences, it's not a chunk — it's a phase. Break it down further. Each chunk should be small enough that the AI gets it right on the first or second try. If a chunk takes 5+ correction rounds, it was too big — split it in half.
Step 3: sequence chunks — most uncertain first (5 min)
Order chunks so the most uncertain features come first. If you're not sure the AI can handle a feature, test it early. If it fails, you find out before building 4 easy chunks on top of a broken foundation.
- Good sequencing: Most uncertain → most certain
- Bad sequencing: Easiest first → hardest last (you build 4 easy chunks, then discover the AI can't do the hard one)
Write in your file:
## Sequencing
Reordered chunks (most uncertain first):
1. [chunk name] — why it's uncertain: [reason]
2. [chunk name]
3. [chunk name]
...
Step 4: write a spec for chunk 1 only (5 min)
Write a full 5-part spec (from Lesson 01) for just your MVP chunk. This is the only chunk you build today.
Write in your file:
## Chunk 1 Spec
[Your 5-part spec for the MVP only]
Step 5: build and test chunk 1 (10 min)
Paste the spec into your AI tool. Build. Test it. Does the MVP work?
Write in your file:
## Chunk 1 Build Result
Did it work? [yes/no]
What needed correction? [list]
Is this a solid foundation to add chunk 2? [yes/no]
Your "add tasks to a project" chunk has needed five correction rounds and still isn't right. What does the chunking rule say?
Each chunk should land in one or two tries. Five or more rounds means it wasn't a chunk; split it and rebuild the smaller piece.