Agency Agency Start Docs GitLab Hub

Docs

How the loop works. Install steps live on Start.

What it is

@slopkit/agency is Flue agents, a GitLab CI sync template, and an acceptor that feeds workers you run. Child repos keep application code at the root. Kit state lives under .slopkit/.

License is AGPL-3.0. Source is dev-agency/gitlab-agency.

Models

Bring your own key. Resolution order:

  1. Package default
  2. FLUE_MODEL
  3. model in .slopkit/config.ts
  4. Optional per-agent override in that same config

Any Flue-supported provider works if the worker has the matching secret.

.slopkit/

Config, specs, plans, notes, and optional agent or skill overlays live here. Edit locally. Push runs kit:sync-push and updates GitLab issues and merge requests. Issue comments sync back through the webhook job. Conversations land in notes.md beside each work item.

.slopkit/
  config.ts
  specs/<slug>/SPEC.md
  plans/epics/…
  plans/…/tasks/…
  agents/   # optional
  skills/   # optional

Status

Status is a state machine. Agents call mr_set_status. That call also undrafts, GitLab-approves, or requests changes as side effects.

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

Dispatch

The acceptor enqueues from:

Bot and kit-* authors are ignored on enqueue.

Staged split on merge. kit::spec merge enqueues scaffolder split. kit::epic merge enqueues epic-split. Then planners and developers pick up the task MRs. Other default-branch merges, and direct pushes to that branch, start Barbara for a docs pass.

Runtime

You run two Push apps from the product repo. See Start for the order. Secrets stay in relay/README.md.

Child CI covers sync, package, and deploy. Agents run on the workers. MR pipelines run the sync include. Comment and label events enqueue acceptor jobs.

Overlay

Optional GitLab CE view partials in gitlab-overlay/ add design approval in the issuable sidebar and agent transcripts in the MR reports tab. They overlay app/views.