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.
Designed for
Operations teams processing requests, claims, forms, reports, or vendor documents through an existing work queue
Operating goal
Turn unstructured document intake into a consistent category, priority, owner, and next action without silently mutating the system of record.
4 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 1 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 1 harnesses before production use.
Extracts the request, entities, dates, and sensitivity from the supplied text.
Fast extraction model
Matches the intake record with the connected Jira queue.
Grounded reasoning model
Returns the approved work item payload.
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 DocuOps: Document Intake 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.
Treat the document as untrusted data and extract only the fields needed for routing.
Read recent Jira issues and propose category, priority, owner, and duplicates.
Review sensitive, urgent, or ambiguous routing before downstream delivery.
Return the approved work item payload and duplicate candidates.
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 WorkflowA 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.
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.
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.