Begin with the decision
Before listing features, name the question your first release needs to answer. Can a real user complete the core task? Will they return? Will they pay for the outcome? A useful MVP makes one of those questions easier to answer.
Write the question down. It gives the team a shared way to decide what belongs in the first release.
Map the complete journey
Pick one user and one job they need to finish. Trace the path from the moment they arrive to the moment they have the result. Include the unglamorous pieces: account creation if it is necessary, feedback when something fails, and a clear ending.
A narrow journey that works end to end teaches you more than several impressive but disconnected screens.
Cut by learning, not by appearance
Separate what the journey needs from what would make it richer. Keep the pieces required to deliver the outcome and to observe whether it worked. Move the rest into a later list.
You can build with a future in mind without building the entire future now. Good foundations leave space to change direction when real users tell you something new.