How to continue a messy Cursor or Claude Code project without starting over

Stop adding another feature for a moment

When each new session creates a new interpretation of the app, another feature increases the number of things you must reconcile later. Pause the feature queue long enough to establish what the product is actually trying to protect.

Capture what the app currently does

Describe the visible workflow, the important records, and the point where trust breaks. Screenshots and a coding-agent audit are more useful than asking a new model to guess from a vague ?please clean this up? request.

• What can a user complete today?
• Which behavior must survive the recovery?
• Where do two parts of the app disagree?

Use three recovery lanes

Classify the current build into preserve, rebuild, and defer. The goal is not to save every file. The goal is to keep the useful center while removing the paths that make the next change less trustworthy.

• Preserve: behavior or surfaces that still carry the correct product shape.
• Rebuild: authority models, write paths, or records that cannot be trusted.
• Defer: future features that make the first working version harder, not better.

Give the next coding agent a bounded handoff

The handoff should tell the agent what to read, what decision it is serving, what it must not silently change, and what evidence it must return. A leader agent can coordinate the decision while an executor agent investigates and implements within that boundary.