Agent Team template
A Devin-style engineering workflow that turns a scoped ticket into a branch, implementation plan, code changes, test run, and pull request draft with review evidence.
One-message setup · 3 specialists · Instant sample
Designed for
AI product teams that want a coding agent with visible scope, tests, and review gates before a PR reaches humans
Outcome
Convert well-scoped issues into reviewable pull requests while preserving ownership, tests, and rollback context.
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.
Decides whether a ticket is small and safe enough for autonomous implementation.
Reasoning model
Plans and applies the implementation on a dedicated branch.
Code-specialist model
Runs checks and turns failures into fix attempts or handoff notes.
Code reasoning model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A coding skill for turning a small ticket into a branch, patch, tests, and PR notes without scope creep.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes repository roots, file reads, diff summaries, test commands, and PR draft operations.
tools · resources · roots
Validate ticket clarity, ownership, and blast radius.
Identify files, tests, and rollback notes before editing.
Make minimal code changes on a dedicated branch.
Run lint, typecheck, and targeted tests.
Open it in Codelit and describe the result. Codelit handles common setup while Flow stays available for direct editing and Activity keeps the proof.
Try agentTurns 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.
Correlates Sentry, Datadog, PagerDuty, and deployment evidence, proposes one bounded mitigation, pauses on the exact actions, and leaves status proof for responders.
A Claude Code-style workflow for scoped engineering maintenance: it reads issues, loads repo context, plans a narrow patch, runs checks, and opens a reviewable PR with evidence instead of pretending the merge is done.