gates plugins

by minipuft

Model Context Protocol (MCP) server for versioned prompt templates, multi-step workflow chains, and quality gates. Symbolic syntax: >>prompt --> >>chain @framework :: 'gate'

by antonygiomarxdev

Skill plus policy directory: role definitions and gate scripts that turn one AI session into a coordinator dispatching specialised workers through Orca

by Dusty Mumphrey

Orka is a multi-agent engineering harness for Codex and Claude Code: resilient Jira sprint scheduling, ticket decomposition, isolated implementation, bounded reviews, and merge-on-green.

by zot24

Run a control tower over a fleet of herdr agents — delegate every project task to a pane, dispatch from a spec file, watch a completion marker, staff only the required seats, and verify through acceptance gates so 'done' is an exit code, not a claim.

by Devrik

Deterministic gates for Claude Code: destructive-command blocks, protected paths, delegation briefs, spec-driven flow and session-start validation. Selection lives in config, not in code.

by Job Schepers

The host-neutral delivery engine: 4 flow-* staged procedures named for what changes — the code, the devbook folders, the dependencies, the project — 3 shared phases, and the pull-request lane, sequenced by the flow-runner agent through a closed set of extension points — spec, implement, validate, app.start, qa.run, verify and deliver as services, session.start, flow.start, data.prepare and flow.end as chores — with human gates a repository adds but never removes, and a run surface resolved from the live tool list so none is a normal outcome. Bindings, extensions, policy, and gates are declared per repository in .devbook/config.json.

by Galileo Studio

Implement, review, and deliver an approved plan slice by slice through Worker and Reviewer subagents: a test gate on the Worker, a read-only Reviewer, and a human-approval prompt for commands that deploy, publish, change shared state, or destroy work.

by Job Schepers

The host-neutral delivery engine: 16 flow-* staged procedures, five of them one per devbook folder, 3 shared phases, and the pull-request lane, sequenced by the flow-runner agent through a closed set of extension points — spec, implement, verify, app.start, qa.run and deliver as services, session.start, flow.start, data.prepare, docs.update and flow.end as chores — with human gates a repository adds but never removes, and a run surface resolved from the live tool list so none is a normal outcome. Bindings, extensions, policy, and gates are declared per repository in .devbook/config.json.

by Jatin Pavagadhi

Ticket lifecycle gates, MR self-review, multi-stack security audit, video-to-bug-report, and large-codebase map-reduce

by Jeon Kwangha

A harness that cannot start without interviewing you and cannot finish without evidence. The phase lives in one .midnight/prd.md and hooks guard its transitions.

by YWR Labs Inc.

Claude Code platform guards, the adversarial code-review standard, and a docs-as-code scaffold — portable across repos and stacks