Orchestrate plans through implementation and PR completion #27

New Issue

2026-10-06T11:56:14-04:00

steve commented

2026-10-06 11:56:14 -04:00

Destination

A reusable orchestrator skill accepts a plan/map from the current context or an @file reference, generates and publishes a spec, breaks it into tracker tickets, then drives those tickets through implementation, four-axis review, and merge to completion.

Notes

Domain: Pi skills, Herdr-managed agent work, Git worktrees, and the project's issue tracker.
Consult: wayfinder, to-spec, to-tickets, herdr, orchestrate-herdr, dual-review, code-review, pr, forge-cli, worktrees, effective-agent-skills, writing-for-agents.
Run one task ticket at a time. Use the current directory as the repo locally; remotely clone to ~/worktrees/<owner>/<repo> when missing and use the canonical .bare layout.
Use the existing spec/ticket/review skills; make to-spec, to-tickets, and dual-review agent-invokable.
Reviews: one dual-review plus one code-review; all four axes must pass. Use needs-review for human-interaction PRs and ready-for-agent to resume within this spec's linked ticket/PR scope.
CI does not exist on the current forge; building CI is out of scope, but require it when available.

Decisions so far

Set bounded retries and human escalation policy: Retry transient failures only; reconcile uncertain side effects and escalate when limits or human judgment require it.
Define terminal cleanup and parent-spec lifecycle: Close only after verified completion; retain authoritative worker-node state and clean up only safe, run-owned resources.

Not yet specified

Tickets

Out of scope

Building the forge CI system; the user will handle that separately.

## Destination A reusable orchestrator skill accepts a plan/map from the current context or an `@file` reference, generates and publishes a spec, breaks it into tracker tickets, then drives those tickets through implementation, four-axis review, and merge to completion. ## Notes - Domain: Pi skills, Herdr-managed agent work, Git worktrees, and the project's issue tracker. - Consult: wayfinder, to-spec, to-tickets, herdr, orchestrate-herdr, dual-review, code-review, pr, forge-cli, worktrees, effective-agent-skills, writing-for-agents. - Run one task ticket at a time. Use the current directory as the repo locally; remotely clone to `~/worktrees/<owner>/<repo>` when missing and use the canonical `.bare` layout. - Use the existing spec/ticket/review skills; make `to-spec`, `to-tickets`, and `dual-review` agent-invokable. - Reviews: one dual-review plus one code-review; all four axes must pass. Use `needs-review` for human-interaction PRs and `ready-for-agent` to resume within this spec's linked ticket/PR scope. - CI does not exist on the current forge; building CI is out of scope, but require it when available. ## Decisions so far - [Set bounded retries and human escalation policy](http://gitea.sagacity.ca/steve/skills/issues/28): Retry transient failures only; reconcile uncertain side effects and escalate when limits or human judgment require it. - [Define terminal cleanup and parent-spec lifecycle](http://gitea.sagacity.ca/steve/skills/issues/29): Close only after verified completion; retain authoritative worker-node state and clean up only safe, run-owned resources. ## Not yet specified ## Tickets - [x] [Set bounded retries and human escalation policy](http://gitea.sagacity.ca/steve/skills/issues/28) - [x] [Define terminal cleanup and parent-spec lifecycle](http://gitea.sagacity.ca/steve/skills/issues/29) ## Out of scope - Building the forge CI system; the user will handle that separately.

steve added the wayfinder:map label 2026-10-06 11:56:14 -04:00

steve referenced this issue

2026-10-06 11:56:37 -04:00

Set bounded retries and human escalation policy #28

steve referenced this issue

2026-10-06 11:56:39 -04:00

Define terminal cleanup and parent-spec lifecycle #29

steve commented

2026-10-06 12:22:25 -04:00

Wayfinding complete: all currently specifiable decisions are resolved, and no fog or open decision tickets remain. The resulting retry and terminal-lifecycle decisions are recorded in Decisions so far. Implementation can proceed from this map.

steve closed this issue

2026-10-06 12:22:29 -04:00

steve referenced this issue

2026-10-06 12:36:53 -04:00

Orchestrate plans from context to merged PRs with Herdr #30

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: steve/skills#27