Orch Goal
Use for a mandatory two-run goal: deliver the original spec, rebuild it from first-run evidence, then deliver the new spec.
Install
$ agentstack add skill-danmcinerney-orchflows-orch-goal ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-danmcinerney-orchflows-orch-goal) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Require: a frozen, routing-stamped [spec](../../../contracts/spec.md) stamped pattern: deliver whose evidence names the original user request by identity, and a goal bound reserving separate budgets for delivery 1, re-specification, and delivery 2.
Run orch-deliver twice, naming the orch-planner profile per [rules/roles.md](../../../rules/roles.md) §4. Delivery 1 runs the original spec. Its status never omits delivery 2 when its contracted Return and durable artifacts can support re-specification; otherwise return its partial evidence under [rules/composition.md](../../../rules/composition.md) rule 8.
Converge delivery 1 through the [goal second-pass design](references/second-pass.md). Run orch-spec with the same profile, supplying the exact original request as its request and the original spec plus that packet as evidence. It writes a fresh pattern: deliver spec with a new run id, the original pack, and delivery 2's reserved bound. Delivery 2 runs that spec once; its final verification and status close the goal.
Never: edit the original spec, omit delivery 2 because delivery 1 passed, widen the original request from discovered scope, or dispatch a third delivery.
Return: status, original and replacement spec identities, both deliveries' status, result identity, changed artifacts, and final verification, the second-pass packet, queued scope, and bounds spent.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DanMcInerney
- Source: DanMcInerney/orchflows
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.