Orch Tdd
Implement one code ticket through red-green slices against its completion test. The code pack's unit executor.
Install
$ agentstack add skill-danmcinerney-orchflows-orch-tdd ✓ 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-tdd) 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: one claimed code [ticket](../../../contracts/work-item.md) and an isolated workspace at a clean baseline.
Slice the objective so each slice is provable by one failing check. Per slice: write the check, watch it fail for the stated reason, make it pass with the least code that honestly passes, then reconcile with the workspace's idiom and shape per the ticket's craft reference. Test at public seams; rewrite any tautological check. Commit each verified slice. Close by running the ticket's full completion test through orch-verify against the result's fixed identity.
Never: write code before its failing check; weaken a check to pass it; leave the workspace off a committed baseline; touch paths outside the ticket's write scope.
Return: the completed ticket per [work-item.md](../../../contracts/work-item.md)'s filing law.
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.