Find the real state
What does the project actually do right now? What is working, what is failing, and what is only pretending to work?
Project recovery
Bring the project back to a clear path.
If a software project is unfinished, unstable, or too confusing to continue, the first job is not to add more features. The first job is to understand what is already there.
Separate symptoms from causes
A visible error is not always the real failure. I look for the path that causes the break.
Protect what is worth keeping
Good pieces should not be destroyed by random rewrites. The repair path should preserve working logic where possible.
Make the next move clear
The goal is a practical next step: fix, refactor, secure, document, deploy, pause, or rebuild only the part that needs rebuilding.
Project recovery is about direction first.