AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Orch Deliver

skill-danmcinerney-orchflows-orch-deliver · by DanMcInerney

Take one stamped spec to a verified deliverable through plan, rolling frontier, one gate, and a final verification. Any pack, one body.

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-danmcinerney-orchflows-orch-deliver

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-danmcinerney-orchflows-orch-deliver)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Orch Deliver? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Require: a frozen, routing-stamped [spec](../../../contracts/spec.md). This body never names a domain; every domain fact comes from the stamped pack's cells.

Open the run: orch-worklog, then orch-workspace for the run's target per the pack's workspace cell. Decompose through orch-decompose; a returned decision_gap rides this body's own Return and routes to the caller.

Plan gate: when the caller asked for a plan, or the spec sets plan_gate, stop here and return the plan — items, edges, budgets, risks, uncovered remainder. Execution resumes only on approval, against the frozen plan.

Execute the graph through orch-frontier. When the frontier exits carrying a failed, blocked, or unparked-open item, set the worklog terminal state through orch-worklog and return per [rules/composition.md](../../../rules/composition.md) rule 8 without crossing the gate. A parked-only remainder returns the same way but leaves terminal empty — the run stays open; re-invoked on an open run, this body skips decomposition and re-enters the frontier over the existing tickets; the gate crosses only once every unit item is complete. Otherwise the terminal assembly item, if the pack declares one, runs last and invalidates unit verification it rewrites, per [rules/topology.md](../../../rules/topology.md) rule 4 — the gate re-verifies the assembled artifact. Cross one orch-review-fix gate, supplying its Require by name: the fixed result identity (the assembled artifact), the pack's stamped lens, the pack's oracle policy, the spec, the standards owner by pointer where the workspace names one, the pack's craft reference, and the write scope; record anything it queues into the worklog's queued_scope. Finish with orch-verify over the spec's acceptance under the pack's oracle policy, reusing the gate's covered verdicts and verifying only uncovered criteria per [rules/verification.md](../../../rules/verification.md) §7; a judged or evidence overall verdict is reported as such, never laundered into a deterministic green. Set the worklog terminal state through orch-worklog at close.

Never: edit the spec; run a second gate; end a judged run on its own claimed green; cross the gate with an open unit item.

Return: status, result identity, changed artifacts, final verification, uncovered remainder, decision_gap, anything the gate queued, and feedback.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.