Dely plugin
A plugin that takes a change through design you approve, an implementer, an independent reviewer and a pull request you merge
- 96 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The implementer edits project code and Control creates branches and pull requests on your behalf
- Worker sessions run in Orca and get trust for the project folder, and OMP never asks the trust question
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/delyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The implementer edits project code and Control creates branches and pull requests on your behalf
- Worker sessions run in Orca and get trust for the project folder, and OMP never asks the trust question
This is third-party code. Review the repository files before installing.
What it does
Dely organizes delivering a change with three sessions on top of Orca. You ask for a change, the Control session writes a design and waits for your approval, then starts an implementer who makes the edits and a reviewer who checks the result independently before the pull request. Control opens the pull request and merging stays with you. Each role gets its own harness and model through `dely:setup`: Claude Code, Codex CLI, GitHub Copilot CLI, OMP, Pi and others, with some harnesses carrying caveats such as the folder trust question. Investigation with no delivery is called a Spike. The plugin is installed only in the harness you talk to and is invoked as `/dely:delivery` or `/dely:setup`.
Who it is for. Developers who want to split design, implementation and review across sessions of different agents while keeping approval and merge for themselves.
Good fit when
- A design document with your approval is needed before the first line of code.
- The implementer and reviewer are best handed to different models, for example Codex writes and Claude reviews.
- Before merging an independent review of changes by a separate session is needed.
- Only an investigation with no delivery is needed: a Spike fits.
Not a fit when
- You need a one-line fix: three sessions and waiting for approval are too heavy.
- Orca is not installed or orchestration cannot be enabled in it.
- Your harness is unsupported: with Kiro CLI workers never start in Orca.
Example request
/dely:delivery: add CSV export of the report, show the design and wait for my approval.Limitations
Orca is required: a desktop app with a registered CLI and orchestration enabled in experimental settings. Codex CLI needs version 0.159.2 or newer with Orca 1.4.217 or newer, and automatic folder trust for Claude Code needs Orca 1.4.220 or newer. The Kiro CLI harness is unsupported, OMP and Pi carry caveats, OMP never shows a trust question so use it only in trusted repositories. Node 18 or newer is required. Before the first delivery open the chosen harnesses once in the project and answer the trust question.
How to disable. Run `claude plugin uninstall dely` or the matching removal in your harness. The project `.dely/pins.json` file and entries in `AGENTS.md` are removed by hand.
FAQ
Who does what?
Control writes the design and opens the pull request, the implementer makes the edits and the reviewer checks independently. You approve the design and merge.
Where do I install the plugin?
Only in the harness you talk to, that is Control. Worker sessions need only Orca and their own login and they read no Dely skill.
How do I choose role models?
With `dely:setup`, which assigns a harness and model to each role or uses the project pins in `.dely/pins.json`.
What is a Spike?
An investigation with no delivery. A Spike that dispatches workers opens its own Orca run and keeps files in that run's folder.
How do I check Orca?
With `orca open`, `orca status --json` and `orca orchestration run-list --json`. On Linux the binary is `orca-ide`.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin that turns on a Delphi expert mode: code style, audit, review, DUnitX tests and end-to-end app checks
A plugin makes the agent explain its code and, before a push, ask questions so you understand what you are merging.
Espalier finds a codebase's unwritten conventions and records them as rules, reviewers and hooks for Claude Code, Codex, Copilot
ADLC Harness takes a task from intent to PR with one command, and the human approves only four key gates.
The AI-SDLC plugin for Claude Code carries a task from spec to PR: a readiness gate, a developer agent and several reviewers.
The ce plugin for Claude Code and Codex: eleven skills and four sub-agents for plans, review, tests, architecture and writing.
README in short
The README goes from a quick start to the three-role flow, the table of supported harnesses, Orca and Dely installation and project setup. A log and troubleshooting follow.