feat: orchestrate plans with Herdr #31

Merged
steve merged 3 commits from issue-30-orchestrate-plans-from-context-to-merged-prs-with-herdr into master 2026-10-06 13:33:54 -04:00
Owner

Summary

Add an explicitly invoked Pi skill to orchestrate plans through publication and task delivery:

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: #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

## 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
steve added 3 commits 2026-10-06 12:52:25 -04:00
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.
steve merged commit 4d39989424 into master 2026-10-06 13:33:54 -04:00
steve deleted branch issue-30-orchestrate-plans-from-context-to-merged-prs-with-herdr 2026-10-06 13:33:54 -04:00
Sign in to join this conversation.