How AI Agents Take a Jira Ticket to Production

Resumen

Pixel shares an architecture walkthrough following Jira ticket PLAT-412, a public API rate-limiting task, from quarterly goals through planning, coding, testing, review, and production release. It explains agent roles, budgets, human approval gates, and software-enforced controls that help teams use AI agents safely and effectively.

DEV Community

One Jira Ticket Through an Org of AI Agents: The Architecture

Following a single story from the board's goal to merged code, through PM clarification, estimation, budgets, risk gates and scorecards. In the last post I sketched an org chart for AI agents: seats that a human or an agent can fill, capacity split down by percentage, probation and benching, and a human overseer on every agent seat. The most common question was: "OK, but what actually happens when a ticket shows up?" So this post follows one ticket all the way through. It's PLAT-412: "Rate limit the public /export API", and we go from the board's quarterly goal to merged code in production. 👉 Interactive diagrams: probita-ai.github.io/agent-org-model/architecture.html The one rule behind everything Agents run in one layer. Everything that limits them is plain software. Every tool call passes a policy engine. Every model call passes a metered gateway. The kill switch revokes keys at those two points. Stopping an agent never depends on the agent cooperating. No model sits in the decision path for budgets, permissions or approvals. Every level adds something before handing down Level Seat Hands down Board Humans $10,000/month, goal "−50% API incidents" CEO Human + copilot agent Engineering 40% ($4,000) CTO Human Epic PLAT-EPIC-40, Platform crew 60% ($2,400) PM Human + PM-assist agent PLAT-412 with 3 acceptance criteria Platform Lead Agent, L2 (suggests, human approves) Assignment + brief to coder-1 Coder Agent, L3 PR, 5 points, P90 $28 Tester Agent, L3 Report + 3 tests the coder didn't write Reviewer Agent, L3, 10% human-sampled Approval Release Lead prepares, human approves Staged flag rollout HR / Finance Staff agents Actuals, scorecard update Every seat uses the same card: what comes in, what it decides, what it hands out, when it escalates, and what it's scored on. That consistency is what makes it possible to swap a human for an agent (or back) in one field. Inside the coder: 12 phases This is where most people's mental model of "an AI coder" is too thin. "Read ticket, write code" skips the parts that make human engineers good. Intake. Reserve budget, read the brief from the lead. Understand. Build an understanding doc: restated goal, code map, blast radius, unknowns. Definition of Ready. Is the ticket buildable? Clarify with PM. (More below.) Estimate. (More below.) Plan. For medium-risk work, the reviewer approves the plan before code. That costs about $0.40 and saves about $15 of wrong-direction work. Implement. Sandbox, test first, checkpoint after every green commit. Self-check. PR checklist, mostly deterministic. Hand off. PR plus two structured briefs (tester, reviewer). Review loop. Max 3 rounds, then escalate. Release gate. A human approves production. Close and learn. Record actuals; propose a lesson to crew memory. The single most useful rule is in phase 2: map every acceptance criterion to a concrete test. Any criterion that can't be mapped is marked ambiguous. That one check catches most unclear tickets before anyone writes code. The coder also has hard stop rules, enforced by the orchestrator rather than the prompt: Same error 3 times → escalate with the trace 80% of budget → pause and re-estimate 100% → the gateway refuses further calls Diff touches files outside the plan → flagged for review More than 120 steps → pause Talking to the PM PLAT-412 says "limits configurable per plan tier." Per user? Per org? Per API key? The ticket doesn't say. Which is realistic. The coder sends one batch of questions, not a drip: type: question_batch
estimated_pm_minutes: 4
questions:
- id: q1
blocking: true
text: "What should the limit be keyed on?"
options:
a: "API key (matches how /export authenticates)" # default
b: "Organization"
c: "User"
why: "Changes the Redis key design and what customers see."
- id: q3
blocking: false
text: "Build the dashboard, or emit a metric ops adds?"
options:
a: "Emit metric only" # default
b: "B...
How AI Agents Take a Jira Ticket to Production
Powered by Readybot.io

Lo último de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …