Brief to tracker issue

An agent turns a brief into a Linear or Jira issue, which is filed after the autonomy policy — and a person, where the policy asks for one — allows it.

Template	create-issue-from-brief
Works on	An issue tracker (Linear or Jira)
Where a person acts	Approve issue creation — a person approves or rejects, waiting up to 24h
Agents it calls by name	issueDrafter

The workflow

Drawn from the template spec at build time. Bookkeeping nodes that only record status are left out; amber nodes are where a person acts.

flowchart TD
  n_draftIssue[["Draft issue<br/><small>agent: issueDrafter</small>"]]
  n_publishOutcome["Publish outcome"]
  n_checkAuto{"Check auto?"}
  n_humanApproval>"Approve issue creation<br/><small>person: approval</small>"]
  n_autoWrite["Auto write"]
  n_manualWrite["Manual write"]
  n_doneRejected(["Done<br/><small>done rejected</small>"])
  n_done(["Done"])
  n_draftIssue --> n_publishOutcome
  n_publishOutcome --> n_checkAuto
  n_checkAuto -->|"yes"| n_humanApproval
  n_checkAuto -->|"no"| n_autoWrite
  n_humanApproval -->|"approved"| n_manualWrite
  n_humanApproval -->|"rejected"| n_doneRejected
  n_humanApproval -->|"timed out"| n_doneRejected
  n_autoWrite --> n_done
  n_manualWrite --> n_done
  class n_humanApproval gate

Maturity: seeded, not yet proven

Seeded content rather than a proven flow. The connector, the agents, and the governance it relies on exist, but only the engineering flow has a complete, exercised end-to-end path today. See product overview §8.

Use it

Every built-in template is seeded into the workflow library and can be cloned, edited on the visual canvas, and versioned — see architecture for the node types. The spec lives in packages/shared/src/workflow/templates/createIssueFromBrief.ts.