Full workflow
Use the narrative brief first, then execute the step summary in order.
When to use this workflow
Use this when a Replit app is useful enough to leave the playground. The hard part is not copying files. The hard part is replacing implicit Replit conveniences with explicit production decisions.
Production checklist
Cover these areas before launch:
- Runtime and start command.
- Build command and artifact location.
- Environment variables by environment.
- Database, migrations, backups, and seed strategy.
- Upload and file persistence.
- Auth sessions, cookies, and redirect URLs.
- Email, payments, queues, cron jobs, and webhooks.
- Logs, alerts, rollback, and owner escalation.
Agent handoff prompt
text
Audit this Replit app for production migration.
Do not rewrite code yet.
Create a checklist of Replit-specific assumptions, missing environment separation, persistence risks, deployment blockers, and operational runbook gaps.
Then rank the fixes by launch risk.Migration rehearsal
Do at least one preview deployment before production. Seed non-sensitive test data, exercise auth, submit forms, trigger webhooks, and verify logs. If a step cannot be observed, it is not production ready.
Done criteria
The app is ready to leave Replit when production configuration is explicit, persistence does not depend on the workspace filesystem, secrets are separated, deployment is repeatable, and rollback is documented.