The problem
What was broken before AI
Many engineering tasks are small enough to be annoying but still require context: fixing copy, updating documentation, changing a configuration, adding a small feature, or making a routine code adjustment. The work is not always hard, but it still interrupts someone, requires switching tools, and competes with higher-priority engineering time. At a large company, those small requests can pile up across teams.
What changed
What the use case made possible
Stripe Minions moves the first step of that work into Slack. A teammate can trigger an agent from the conversation where the need appears. The agent uses coding tools to make the change and then opens a pull request. That keeps the workflow lightweight for the person making the request, while preserving the engineering review process that makes the result safer to accept.
Why this matters
Why this use case is worth studying
Steve’s use case is useful because it shows AI agents fitting into an existing team workflow instead of replacing it. The agent does the first pass. Slack provides the front door. GitHub-style review provides the guardrail. That combination matters: the team gets leverage from AI without pretending the model should make final decisions on its own.
Use this when
When this pattern applies
Use this pattern when small engineering requests already appear in chat and frequently interrupt the people who know how to make the change. It works best for narrow, reviewable tasks where an agent can prepare a first draft but a human should still approve the final result.
