Orch Spec
Turn a request plus evidence into a routing-stamped, decomposition-ready spec. Use before any delivery run.
Install
$ agentstack add skill-danmcinerney-orchflows-orch-spec ✓ 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-spec) 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: the request, and access to the workspace or evidence it concerns.
Gather the facts a spec depends on through orch-investigate — one bounded question: what exists, what constrains, what the request actually touches. Settle the decisions only the user can make through orch-elicit; synthesize settled decisions without re-interviewing. Verify cheap claims; mark the rest assumptions.
Draft the spec per [contracts/spec.md](../../../contracts/spec.md), holding its two hard lines: the objective is one observable end state, never activities, and a criterion no oracle can check is a spec defect to fix here, not the decomposer's slack. The spec's exact nouns and verbs come from [docs/vocabulary.md](../../../docs/vocabulary.md) and the craft cell of the pack the stamp will name — they become the deliverable's searchable names.
Stamp routing — pattern by shape of done and exactly one pack per [rules/topology.md](../../../rules/topology.md) — and carry the stamped pack's required fields. Write the accepted spec to .orch/runs//spec-.md; the run itself — worklog, tickets, terminal state — opens at delivery, not at spec time.
Never: stamp two packs (chain two specs instead); leave an acceptance criterion oracle-less; restate standards an exemplar's owner already states.
Return: the accepted spec path, decisions, assumptions, and evidence consulted.
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.