Agency Agency Start Docs GitLab Hub

SlopKit Agency

Build your own agent development team.

Open source. Bring your own key. Point it at any provider and any model. Six named GitLab users work the merge request. They open drafts, comment as themselves, and move kit and status labels. You run the stack. You keep the keys.

Get it running How the loop works Source

AGPL source

Fork the package. The license is AGPL-3.0.

Your API keys

Workers read the provider secret from your cluster.

Any Flue model

Set FLUE_MODEL or model in .slopkit/config.ts.

Who this is for

GitLab is the office. Your model key stays yours.

On GitLab

Comments and labels dispatch a named team on the merge request.

Your model

Set the provider key on the workers. Point Agency at the model you use.

Call sheet

Meet the team

Named GitLab users. They mention each other with @kit-*. Add more under .slopkit/agents/.

  1. Scaffolder

    Richard

    @kit-scaffolder

    Sizes a spec into one kit::task, or into epics that split on merge.

  2. Planner

    Hermione

    @kit-planner

    Deepens the plan on the merge request before implementation starts.

  3. Developer

    Elliot

    @kit-developer

    Implements on the plan branch. Marks the MR ready for review.

  4. Reviewer

    Gilfoyle

    @kit-reviewer

    Requests changes or approves on the merge request.

  5. Tester

    Donna

    @kit-tester

    Checks the preview. Sends it back or deploy-approves.

  6. Documenter

    Barbara

    @kit-documenter

    After merge or a direct push, inventories docs. Writes a follow-up or skips. Always leaves a note.

  7. Custom

    Create your own

    .slopkit/agents/

    Add a role, a persona, and a GitLab identity for your project.

The loop

Merge webhooks stage the split. You run a webhook acceptor that enqueues work. Workers claim jobs and run Flue in a devenv sandbox.

1

Spec merge request

Richard refines a kit::spec until a human marks it ready and merges it.

2

Split

That merge enqueues scaffolder split. Tiny specs become one task. Larger specs become epics. Epic merge then opens tasks.

3

Plan, then implement

Hermione deepens the plan on the same MR Elliot will code on.

4

Review and test

Gilfoyle and Donna cycle until the work ships or hits the budget.

5

Document

After the feature lands, Barbara inventories README, docs, and wiki. She opens a docs MR or writes why she skipped.

Hard limits

The loop has a budget. Status moves through one tool.

Five rounds

After five review or test label cycles since the last status::blocked, the next move is blocked. Only a human leaves that state.

One status tool

Agents call mr_set_status. Draft, approve, and request-changes are side effects of that call.

How work wakes

Dispatch comes from kit and status labels, optional @kit-* mentions, and the previous note's agent when that differs.

Want a team you can fork?

Deploy the acceptor and workers on your cluster, set your provider key, include the CI template. Start has the YAML.

Get it running Product source