Before: no unified orchestration entry point; state could be committed accidentally.
After: Ruby YAML frontmatter checks and git diff --check pass; git check-ignore -v .orchestrate/example/state.json confirms run state is ignored.
Live Pi + Herdr end-to-end acceptance was not run; this Markdown-only repository has no runtime test harness.
Merge Danger
Door: Two-way
Blast Radius: Skills
## Summary
Add an explicitly invoked Pi skill to orchestrate plans through publication and task delivery:
```text
context / @file
→ spec + linked tickets
→ isolated, one-at-a-time implementation + verification
→ four-axis review + gated merge
```
Key changes:
- Add `orchestrate-herdr` with worker-node discovery, run loop, recovery, persistence, escalation, and owned-only cleanup.
- Add `dual-review`; make `to-spec` and `to-tickets` agent-invocable.
- Ignore retained `.orchestrate/` run state.
- Leave Cursor `/orchestrate` unchanged.
Ticket: http://gitea.sagacity.ca/steve/skills/issues/30
## Evidence
- **Before:** no unified orchestration entry point; state could be committed accidentally.
- **After:** Ruby YAML frontmatter checks and `git diff --check` pass; `git check-ignore -v .orchestrate/example/state.json` confirms run state is ignored.
- Live Pi + Herdr end-to-end acceptance was not run; this Markdown-only repository has no runtime test harness.
## Merge Danger
**Door:** Two-way
**Blast Radius:** Skills
Add an explicitly invoked Pi orchestration skill that drives a plan from the
current conversation or an @file through a published spec, linked dependency-aware
tickets, and one-at-a-time isolated implementation to a merged PR, using Herdr
and Pi agents with no Bun CLI or orchestration runtime.
- orchestrate-herdr (SKILL.md + dispatcher/run-loop/state references): worker-node
selection and Herdr discovery/validation, plan-and-publish, one-at-a-time task
loop (claim, isolate, implement, verify, four-axis review, scoped fix rounds max
three, transient retries max two, reconcile uncertain side effects, escalate),
PR/merge/close gates, authoritative worker-node state, cross-system recovery,
and owned-only cleanup that preserves dirty worktrees and retained state.
- dual-review: self-contained correctness/security + maintainability review axis
(four-axis review with code-review).
- to-spec and to-tickets: drop disable-model-invocation so the orchestration
workflow can invoke them.
- READMEs: list the two new skills.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Add an explicitly invoked Pi skill to orchestrate plans through publication and task delivery:
Key changes:
orchestrate-herdrwith worker-node discovery, run loop, recovery, persistence, escalation, and owned-only cleanup.dual-review; maketo-specandto-ticketsagent-invocable..orchestrate/run state./orchestrateunchanged.Ticket: #30
Evidence
git diff --checkpass;git check-ignore -v .orchestrate/example/state.jsonconfirms run state is ignored.Merge Danger
Door: Two-way
Blast Radius: Skills