Agent Team template
Reviews recent deployments for one project, pauses before spending build resources, creates one preview from the latest source, and returns its deployment evidence.
One-message setup · 2 specialists · Live after setup
Designed for
Product and engineering teams that want a safe one-click preview before production promotion
Outcome
Create one approved Vercel preview for the selected project and return a verifiable deployment URL.
Say what should be true when the work is done.
Codelit runs one labeled Sample with no account, model, or external App calls.
Review the evidence, then reuse the same brief with your data when it is useful.
Reads the selected Vercel scope and prepares one bounded outcome.
Balanced reasoning model
Performs one typed Vercel action after showing the exact preview.
Structured output model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for Vercel Preview Deployment Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
tools · resources · prompts
Read the selected Vercel context and prepare the smallest useful action.
Rebuild the selected Vercel project's latest source as a preview deployment.
Open it in Codelit and describe the result. Codelit handles common setup while Flow stays available for direct editing and Activity keeps the proof.
Use this teamCorrelates Sentry, Datadog, PagerDuty, and deployment evidence, proposes one bounded mitigation, pauses on the exact actions, and leaves status proof for responders.
Turns one scoped release request into a reviewed branch artifact, preview deployment, browser-verified result, pull request, production promotion, and Slack proof using the accounts the team already owns.
Read the highest-impact issues and apply one approved status change after diagnosis. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.