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.
Designed for
Operations and engineering teams that turn unstructured requests into an existing Jira queue
Operating goal
Create one evidence-backed Jira task in the selected project with no duplicate on resume.
2 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 2 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 1 harnesses before production use.
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.
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, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowReads 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.
Classifies incoming document text, checks routing and duplicate signals against a connected Jira project, pauses on sensitive cases, and returns an auditable work-queue handoff.
A Slack-native engineering agent that receives operational requests, gathers context from tickets and repos, routes work to specialist agents, and drafts auditable responses before anything risky happens.