Issues in, merged pull requests out
Agentic Workflows are reusable GitHub Actions loops from Plain Concepts Platform. One router turns every GitHub event into one route, and seven agent workers carry an issue from opened to merged. Every route is drawn here.
The router
Every trigger the repository has arrives at one router, and exactly one thing happens per event. Pick an event to follow it, or open the Work Router diagram.
- classifyPure shell, one event in, one route out
- authorizeRead only
- routedispatch-triage, re-enters as the App
- workeragent-triage
The front door for read-only openers. Triage diagram
From issue to merge
The usual path through the chain. Each stage hands off by label, so a route can be added or removed without touching the others. How the routes chain
Triage
Read-only openers come through the front door. Anyone with write skips it.
Refine
Sizes the work. Three to five points goes ahead; eight or more is split into children.
Implement
Writes the code and opens one pull request, then stops. The merge is not its call.
Merge gate
The only worker that merges, one at a time for the whole repository.
Seven workers
Each worker has its own diagram. Pick one to see how its run branches; open it full screen to pan, search and trace.
The front door for issues opened by people with read-only access. Four outcomes, and only one of them closes anything.
Open full screen ↗Router and infrastructure
Around the workers run deterministic jobs. No model runs in any of them: they retry a failure and report a decision.
Docs
How the package is owned, run and shipped.
Install in your repository
Install and configure agent-harness first, then run the interactive installer and pick the loops you want.
npx @plainconceptsplatform/workflows