How the loop works
From a one-line issue to a merged, reviewed PR — the five stages of the Forge pipeline.
Forge is a GitHub-issue-driven loop. Each stage is a scheduled workflow that hands off to the next with a label.
1. Triage
A new issue is classified: priority, complexity, area, type, and which model should handle it. The result is a set of labels and a short rationale.
2. Plan
For anything non-trivial, Forge writes a contractual implementation plan — the files it will touch and the acceptance criteria — and attaches it to the issue.
3. Build
Forge implements the plan on a branch and opens a pull request. If the primary vendor is unavailable, it falls back to another so the backlog never stalls.
4. Review
A different AI vendor reviews the PR and posts a structured review. Blocker or major findings block auto-merge.
5. Merge
Trivial and easy changes that pass review and CI are squash-merged automatically. Everything else waits for your thumbs-up.