Tracking Feature Progress and Status in Lovable Projects

Why feature tracking is not automated in Lovable

Lovable is a code generation tool, not a project management tool. It does not have built-in features for tracking which features are complete, which are in progress, and which are still planned. As your project grows beyond a few pages, it becomes increasingly difficult to remember what has been built, what needs fixing, and what is next on the roadmap. Without tracking, you risk building duplicate features (prompting for something that already exists), forgetting edge cases (a feature works for the happy path but never had error handling added), and losing context between sessions (you return to the project a week later and cannot remember where you left off). The most effective tracking method in Lovable is using AGENTS.md as a project status document. Since the AI reads this file at the start of every session, it serves double duty: tracking progress for you and informing the AI about what exists and what is planned.

• No built-in project management or task tracking in Lovable
• Version history shows code changes but not feature-level progress
• Multiple team members editing without a shared understanding of project status
• Context is lost between sessions — you forget what was built and what remains
• Edge cases and follow-up items are not recorded anywhere

Error messages you might see

Before you start

• A Lovable project with multiple features to build
• A rough list of features you want to implement
• Access to the Lovable editor for creating and updating AGENTS.md

How to fix it

// No tracking — features are lost between sessions

# AGENTS.md — Feature Status
## Core Features
| Feature | Status | Notes |
|---------|--------|-------|
| User registration | Done | Email/password via Supabase Auth |
| User login | Done | With session persistence |
| Dashboard stats | Done | Shows total orders, revenue |
| Orders table | In Progress | Basic table done, needs pagination |
| Search/filter | Planned | Filter by customer name and date |
| CSV export | Planned | Export filtered results |
| Admin panel | Planned | User management, role assignment |
| Email notifications | Blocked | Waiting for Resend API key |

// Chat history is the only record
// Hard to find specific feature implementations in a long chat

# AGENTS.md — Progress Log
## Session: March 24, 2026
- Created registration and login pages
- Connected to Supabase Auth
- Added session persistence with onAuthStateChanged
## Session: March 25, 2026
- Built dashboard page with stats cards
- Created orders table with basic column display
- TODO: Add pagination to orders table
## Next session priorities:
1. Add pagination to orders table
2. Add search/filter functionality
3. Create CSV export feature

// Starting a session without planning:
// Jumping straight into Agent Mode prompts

// Plan Mode sprint planning:
// "I want to complete these features in this session:
// 1. Pagination on the orders table
// 2. Search filter by customer name
// 3. CSV export of filtered results
// Break these into implementation steps and suggest the best order."
//
// AI creates a step-by-step plan → record in AGENTS.md → execute

// Feature marked as 'Done' but edge cases not handled:
// Orders table: works with data but crashes when empty
// Search: works but no 'no results' message

# Follow-up Items
| Feature | Edge Case | Status |
|---------|-----------|--------|
| Orders table | Empty state (no orders) | Planned |
| Orders table | Loading skeleton | Done |
| Orders table | Error state (API failure) | Planned |
| Search filter | No results message | Planned |
| Search filter | Clear search button | Done |
| CSV export | Handle empty filtered results | Planned |

Complete code example

1# Project Roadmap and Status
2
3## Feature Status
4| Feature | Status | Priority | Notes |
5|---------|--------|----------|-------|
6| User registration | Done | High | Email/password via Supabase Auth |
7| User login | Done | High | With session persistence |
8| Dashboard stats | Done | High | Total orders, revenue, customers |
9| Orders table | Done | High | With pagination (10/page) |
10| Search filter | In Progress | Medium | By customer name (real-time) |
11| CSV export | Planned | Medium | Export current filtered view |
12| Admin panel | Planned | Low | User management, roles |
13| Email notifications | Blocked | Medium | Need Resend API key |
14
15## Edge Cases Needed
16- Orders table: empty state, error state
17- Search: no results message, clear button
18- All pages: mobile responsiveness
19- Forms: validation error messages
20
21## Progress Log
22### March 25, 2026
23- Added pagination to orders table
24- Started search filter implementation
25- Next: complete search, add CSV export
26
27### March 24, 2026
28- Built dashboard with stats cards
29- Created orders table with columns
30
31## Coding Conventions
32[...existing coding rules...]

Best practices to prevent this

• Update the feature status table in AGENTS.md after every work session
• Use four status levels: Planned, In Progress, Done, Blocked
• Track edge cases (empty states, error states, loading states) as separate items
• Add a progress log with dates so you can trace when features were built
• Use Plan Mode at the start of each session to plan priorities
• Keep the feature table near the top of AGENTS.md so the AI reads it first
• Mark blocked items with the reason for blocking so you can unblock them later
• Review the feature status weekly to ensure nothing is stuck or forgotten

Still stuck?

Copy one of these prompts to get a personalized, step-by-step explanation.

Related error patterns