| name | deployment-planner |
| description | Plan and execute deployment of the frontend, backend, and database to production. Use when the user asks to deploy, configure hosting, write Dockerfiles, or set up CI/CD. |
| category | deployment |
| version | v1.0 |
| inputs | ["config/stack.config.json","config/env.example","existing frontend/ and backend/"] |
| outputs | ["Dockerfile","CI/CD workflow file","Deployment checklist","Hosting guide"] |
Deployment Planner Skill
Purpose
Prepare and document the full deployment pipeline for Vercel (frontend), Render (backend), and MotherDuck (database).
When To Use
Use this skill when the user asks to:
- Deploy the application to production
- Write a Dockerfile for the backend
- Configure Vercel or Render
- Set up CI/CD via GitHub Actions
- Produce a deployment checklist
Inputs
config/stack.config.json (locked stack)config/env.example (required env vars)- Built frontend in
frontend/
- Built backend in
backend/
Workflow
- Verify environment variables against
config/env.example
- Build frontend (
npm run build)
- Build and containerize backend (
Dockerfile)
- Run database migrations (
alembic upgrade head)
- Run full test suite (
scripts/test-all.sh)
- Configure Vercel project (frontend)
- Configure Render service (backend)
- Deploy preview and smoke test
- Document deployment steps
Deployment Targets
- Frontend: Vercel — auto-deploy from
main branch
- Backend: Render — Python/Docker service
- Database: MotherDuck — managed PostgreSQL
Quality Checklist
Reference
