Run a pipeline
Every requirement runs through the same autonomous pipeline. Here is what happens end to end, typically in about four minutes.
1. Submit
Create a ticket (GitHub issue tagged factory, a Jira ticket, or the dashboard composer). Keep the scope clear and specific for best results.
2. Plan
The planner analyzes your codebase and decomposes the requirement into parallel implementation tasks. If the request is ambiguous, the factory asks a clarifying question before guessing.
3. Build
Each task runs in an isolated container with full Git, terminal, and file system access. Coders work in parallel, each pushing its own branch.
4. Review
Independent reviewer agents verify each task for correctness, security, and style. Review dimensions are checked separately so nothing merges unverified.
5. Ship
The merger combines all approved branches into a single clean pull request with a full description. If Jira is connected, the ticket status is updated.
Costs and performance
- Average ticket-to-PR cycle: ~4 minutes
- Average cost per task: ~$2
- First-pass success rate: 95%+