Agent Team template
Reads one Jira project, converts a request into a scoped work item, pauses on the exact fields, creates it once, and returns the Jira issue proof.
One-message setup · 2 specialists · Live after setup
Designed for
Operations and engineering teams that turn unstructured requests into an existing Jira queue
Outcome
Create one evidence-backed Jira task in the selected project with no duplicate on resume.
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 Jira scope and prepares one bounded outcome.
Balanced reasoning model
Performs one typed Jira 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 Jira Intake-to-Issue 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 Jira context and prepare the smallest useful action.
Create one Task whose summary and description are rendered from the reviewed handoff.
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 teamReads one support ticket, order, and payment, evaluates the request, issues only the approved bounded refund, updates the customer ticket, and leaves financial and support proof.
Reads one Linear team's queue, turns incident evidence into a concise follow-up, pauses on the exact issue, creates it once, and returns Linear proof.
Find a customer ticket, prepare a grounded resolution, and add the approved comment or status update. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.