Install
Inside DeepSeek Harness, with dsh-market
dsh plugin --profile web add dshmarket
Or from the command line
dsh plugin --profile web add github:LeslieWylie/agent-loop-workflow
Installing runs third-party code with your own permissions — it can read your files, use your credentials and reach the network. Review the source first, and pin a commit (github:owner/repo#sha) when you can.
README
What is this
A project-agnostic multi-agent collaboration workflow skeleton. Any agent squad composed of DRI + reviewer + lead + ops can load it to get consistent workflow rules, without duplicating them across every agent's instructions.
Core Capabilities
| Module | Content |
|---|---|
| Role Topology | DRI (doer), reviewer, lead (decision/routing), ops (automation) — four roles with clear responsibility boundaries |
| Loop Guard (6 invariants) | Turn limit, progress stall detection, repeated error fuse, timeout warning, explicit exit gate, single authoritative writer |
| Standard Handoff Format | 6-field handoff template: owner, goal, input, permitted writes, acceptance criteria, failure evidence |
| Risk-based Routing | fast / standard / high lanes, routing to different reviewers based on change scope |
| Delivery Sequence | verify → commit → push → Draft MR/PR → ready signal → in_review (fixed order) |
| Review→Close Protocol | Automatic in_review dispatch, reviewer metadata, reject/retry, escalation |
| Anti-loop Protection | Idempotent issue creation, state-change filtering, human-source-only new task trigger |
| Red Lines | Secret isolation, token permission separation, destructive operation confirmation |
Install
dsh plugin --profile web add "github:LeslieWylie/agent-loop-workflow"
After restart, load the skill in any session:
load agent-loop-workflow
Design Principles
- Project-agnostic: Only defines collaboration flow rules. Project-specific knowledge goes in
*-conventions/*-engineering/*-review-rulesskills - Zero dependencies: No external services required, only the DSH skill loading mechanism
- Forge-agnostic: the skill describes the collaboration flow only. Map its "issue" and "MR" onto whatever tracker and forge you already use — it names none.
License
MIT