Sample Cursor Project Cleanup Triage
This is an illustrative sample of the written triage format. A real delivery uses the buyer's repo export, staging URL, blocker list, and deadline.
Executive Readout
Decision: revise before handoff. The prototype demonstrates the intended workflow, but the current structure makes bug fixing slow and deploy confidence low.
Primary blocker: duplicated state and inconsistent validation across form steps. The demo path works, but edge cases create silent failure states.
Best next move: stabilize the user flow, remove duplicate component branches, and add a minimal QA checklist before any visual polish.
Scope Reviewed
- Project tree and package scripts.
- Main route flow and form state transitions.
- Visible error handling on the staging path.
- Deployment notes, environment variables, and handoff README.
Risk Register
| Priority | Finding | Evidence To Check | Recommended Fix |
|---|---|---|---|
| P1 | Two sources of truth for the same form values. | Compare step-level local state with the final submit payload. | Move the canonical payload into one reducer or form controller, then pass derived values down. |
| P1 | Validation only covers the happy path. | Submit empty, partial, and malformed inputs from each step. | Define shared validation rules and block progression with visible inline errors. |
| P2 | Generated components repeat layout and button logic. | Search for duplicate submit handlers, card wrappers, and modal controls. | Extract one small component per repeated pattern after behavior is stable. |
| P2 | Deployment notes are incomplete. | Run install, build, and preview from a clean checkout. | Add required env vars, known commands, and one verification path to the README. |
Fix Order
- Confirm the expected user path and define the accepted payload shape.
- Stabilize validation and error states before refactoring visuals.
- Remove duplicate branches only after the behavior is covered by manual QA steps.
- Write a handoff note that names what is safe, risky, and still untested.
Buyer Receives
- Plain-English decision: fix, rebuild, or hand off.
- Prioritized risks with evidence to inspect.
- Concrete fix order for the next developer or coding-agent session.
- Short QA checklist for accepting the next version.
Boundaries
This sample is not client work and does not imply a guaranteed launch outcome. The paid triage is bounded operational QA and cleanup planning for one provided target.
Independent operational review. Not affiliated with Cursor.