Intelligent Flow
What it does
Mention Intelligent Flow in a Jira comment or a Slack message. Agents draft the spec, write the tests, build the change and deploy it to staging.
- A fixed control plane decides what runs next, not a model.
- The flow stops at each gate until a named person approves it.
- No agent can merge. A person merges.
- One agent writes the tests and another writes the code. The coding agent cannot change a test.
- Every step leaves a tamper-evident record.
Who it is for
- Delivery teams who want agents to do the work while people approve it.
- Approvers who sign off a spec or a change without running any tools.
- Organisations that must trace every AI-assisted change.
How teams use it
- Describe the repository and its owners in two setup files.
- Connect GitHub, Jira and Slack. Set a model budget.
- Start a work item from Jira or Slack.
- Approve the spec and the build, or send them back.
- Merge the pull request. The change deploys to staging.