Bug Intake Gate
Every bug report is read before it reaches the backlog — and the ones that can't be worked are named, not silently queued.
What it does
Polls the tracker for open issues and records each one in the mission's own table. For every report it judges whether there is enough to start work and, where there is not, names what is missing. One human gate then accepts it into the backlog, sends it back for detail, or parks it — and that judgement is remembered next to the report.
How it works
Every incoming bug report is read before it reaches a backlog. The mission polls the tracker for open issues, records each one, judges whether the report contains enough to start work — and where it does not, says exactly what is missing. One person then accepts it, sends it back for detail, or parks it, and that judgement is remembered alongside the report.
How it's wired
One poll watcher on the tracker's search, storing into `intake`. Two enrichments run by the Triage Analyst — a readiness verdict and what is missing — then one human gate whose three options each write a note back onto the same row. Everything lands on the Triage desk.
The team
Reads an incoming bug report the way a triager does — decides whether there is enough to reproduce and start work, and if not, names precisely what is missing.
Connects to
What it watches
Polls the tracker every two minutes for issues that are still open, and records each new one once.
Human approval
One consequential step waits for a person's approval before it acts.
What it already knows (2)
Data it carries
1 table
What it shows a human
Ask it
“Triage this report: "Checkout fails intermittently for EU customers. No error is shown, the page just reloads."”
“Triage this report: "App is slow."”
“Triage this report: "Export returns an empty CSV when a date filter is applied, since Tuesday, on the reporting screen."”
“What makes a bug report workable, and what would you send back?”
“Given a report with no component and no steps to reproduce, what exactly would you ask the reporter for?”
Before it runs, you'll
- 1Confirm the Issue Tracker server at import. It is credential-free and works as-is; replace the URL with your own Jira, GitLab or other tracker and nothing else changes — the mission only calls search_issues.
- 2Provision the Triage Analyst (pure reasoning — no knowledge base to upload).
- 3Enable the observation, then work the Triage desk: accept, send back, or park each report as it arrives.
Import into StudioX
- Download the
.sxmfile. - In StudioX → Missions → Import, drop the file.
- Review, finalize, and it's live — chat to it or enable the observation.
Reviews
No reviews yet. If you’ve run this mission, yours will be the first — what it handled well, and what you had to wire up, is what the next person needs to know.
More in Engineering
Close-Out Gate
A fix isn't finished until somebody can say what went wrong — and the answer is written down where it can be found again.
RCA Analyst
Defect Twin Finder
Before anyone starts work, the mission says whether this fault has been seen before — and what was learned the last time it was.
Signature Analyst
Change Impact Planner
Every commit is read as the files it actually changed — and what was decided about that area last time is on the screen when you scope this one.
Impact Analyst