# Orch Spec

> Turn a request plus evidence into a routing-stamped, decomposition-ready spec. Use before any delivery run.

- **Type:** Skill
- **Install:** `agentstack add skill-danmcinerney-orchflows-orch-spec`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [DanMcInerney](https://agentstack.voostack.com/s/danmcinerney)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [DanMcInerney](https://github.com/DanMcInerney)
- **Source:** https://github.com/DanMcInerney/orchflows/tree/main/skills/workflows/orch-spec

## Install

```sh
agentstack add skill-danmcinerney-orchflows-orch-spec
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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](https://github.com/DanMcInerney)
- **Source:** [DanMcInerney/orchflows](https://github.com/DanMcInerney/orchflows)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-danmcinerney-orchflows-orch-spec
- Seller: https://agentstack.voostack.com/s/danmcinerney
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.