JOIN

OPEN SOURCE — COMING SOON

JOIN works in the channel, under @join, as a team of agent personas: Scrum Master, Product Owner, UX Designer, Architect, Frontend, UI Pro, BA/SA Pro, and more.

01 The peer team

02 Every role has a human. Every human has a drafter.

In JOIN's configuration (config/join.yaml, a file that belongs to you — never committed, never shipped in a release, never replaced by an update), each Scrum role pairs an accountable human with the persona that drafts for it.

The human stays accountable. The persona is never the role-holder; it drafts that role's section of the spec. Triage brings in only the roles an idea really needs, usually one to three, and they propose in the order their work builds: problem, flows, server, data, components, then the analyst. Approvers are configured separately: only the people listed may approve commits and pull requests, anchors, drafts, and the spend report.

03 Human in control

JOIN's directives are to help create specs. The only commits it makes are spec docs and mockups for developers to utilize.

• Agents write only to that thread's own branch (for example join/JOIN-52) and open a pull request into development for a person to review and merge.
• Nothing reaches the repository until a person merges it.
• Drafts stay in JOIN until an approver saves them, and each reply says what was committed.

04 Agents that give each other feedback. Configured by you.

• Ownership boundaries: each persona's prompt says what it owns in the spec and what it leaves to the others, so every role adds its own section instead of repeating the rest. The UX Designer does not restate the problem or the criteria. The Architect does not restate the problem or the flows, and leaves schema to the DBA and components to Frontend. The DBA builds on the Architect's section. Frontend builds on the UX flows and the Architect's endpoints, and says where they leave a gap.
• Built in sequence: roles propose in order, and each later persona is told who already proposed, so later sections build on, and push against, the earlier ones.
• Relay second opinions: set relay: true on a persona and every answer and proposal gets a second opinion from its next provider. In our configuration the Architect and UI Pro run with relay on.
• Pro reviewers, asked by name: UI Pro reviews and sharpens what the UX Designer wrote rather than starting over, and says which changes matter most. Architect Pro does the same for the Architect. BA/SA Pro goes last, turns the other sections into user stories tied to the Product Owner's acceptance criteria, and lists every conflict or gap between sections and the role that should resolve it.
• Yours to configure, per persona: display name, prompt, preferred providers in order (Anthropic and Gemini), model tier (cheap for triage and summaries, standard for proposals and reviews, frontier for the hardest work), relay on or off, and short aliases such as @join arch and @join ui.
• Noted for accuracy: the configuration includes a debate setting for critique rounds; it is not used yet.

05 What it costs, in the open

Example from a live channel, not a promise — "@join cost":

JOIN's estimate comes from the token counts and the prices in config/join.yaml; each vendor's billing page has the exact amount. When a monthly cap is reached, agents stop and the Scrum Master says so in the thread.

Close

JOIN is coming soon, and it will be open source. Available by request: get in touch through our contact form.

Request JOIN →