The two files you own
Blueprint generates project context, feature specs, and history from two short files you write and maintain. Everything downstream depends on them, so they are worth getting right.
| File | What it is |
|---|---|
blueprint/project-plan.md |
The what and why: problem, users, features, data, stack, and how it ships. A worksheet, not an essay. |
blueprint/build-plan.md |
The ordered feature list: one checkbox line per feature-sized outcome, in rough build order. |
You own both. The AI can help you word and sharpen them, but the decisions are yours. When they change, edit them and re-run /overview rather than hand-editing the generated context.
project-plan.md
Answer each section in a line or two. The goal is a decisive worksheet the overview step can build on, not a specification.
# Project Plan
## 1. Problem - What problem are we solving?
Sticking to daily habits is hard without visible progress.
## 2. Users - Who is this for?
Individuals building personal routines who want a simple daily tracker.
## 3. Features - What does the MVP need?
Create habits, check them off each day, see streaks, and view a weekly summary.
## 4. Data - What are we storing?
Users, habits, and daily completions.
## 5. Tech - What stack are we using?
Next.js, Postgres, and Tailwind. Use whatever stack you prefer.
## 6. Monetize - How will this make money?
Free core tracker, with an optional paid tier for cross-device sync.
## 7. UI/UX - How should this look and feel?
Calm, mobile-first, and fast. One clear action per day.
## 8. Deployment - Where and how will this ship?
Vercel, with Postgres for storage and the standard framework build.build-plan.md
This is the file the build loop tracks, so its shape matters most. It must be a numbered checkbox list where each item is a feature-sized outcome, not a loose task or a whole product area.
# Build Plan
- [ ] 1. **Habit list** - create, rename, and delete habits
- [ ] 2. **Daily check-in** - mark a habit done for today
- [ ] 3. **Streak view** - show current and longest streak per habit
- [ ] 4. **Weekly summary** - completion rate for the past seven days
- [ ] 5. **Deployment readiness** - configure the host and verify the production build/feature with no argument specs the next unchecked item, and completed features get checked off here, so the list doubles as your progress tracker. A large item gets split into sub-items (4a, 4b) when you spec it.
Keep items feature-sized
| Good | Avoid |
|---|---|
Daily check-in - mark a habit done for today |
Database |
Streak view - show current and longest streak |
Make it look nice |
Weekly summary - completion rate for the week |
Habits, streaks, summary, and deploy |
Do not list scaffolding or prototyping as features; those are pre-build steps. Start with your first real slice of functionality.
Before you run overview
Rough bullets are fine on the first pass. /overview checks the plan shape, flags placeholders and vague items, and can propose a cleaned-up checkbox version before generating the project overview. Fill in both files, then run it.