refactor(orchestrate-herdr): scope skill to spec-ticket implementation on a named worker

Rewrite SKILL.md, dispatcher and run-loop references: the skill now takes
<spec-ticket> [worker], always starts fresh agents, and follows the
implement-spec flow (integration branch, frontier tickets, per-task review
and merge) instead of the old plan-and-publish-to-merged-PR pipeline.
Update the engineering README description to match.
This commit is contained in:
2026-10-06 15:59:06 -04:00
parent fa9813daa4
commit abf9b8e7ec
4 changed files with 64 additions and 163 deletions
+1 -1
View File
@@ -13,7 +13,7 @@ Daily code work.
- [implement-spec](implement-spec/SKILL.md) — Implement the result of /to-spec and /to-tickets in code.
- [implementation-orchestrator](implementation-orchestrator/SKILL.md) — Implements ready-for-agent tracker tickets through isolated worktrees, pull requests, review, conflict resolution, and merge. Use after wayfinder and planning have produced tickets, with or without a ticket ID/URL; no ticket ID/URL means process available tickets. Does not create planning tickets.
- [improve-codebase-architecture](improve-codebase-architecture/SKILL.md) — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
- [orchestrate-herdr](orchestrate-herdr/SKILL.md) — Drive a plan from context or @file through a published spec, linked tickets, and one-at-a-time isolated implementation to a merged PR using Herdr and Pi agents.
- [orchestrate-herdr](orchestrate-herdr/SKILL.md) — Implement a published spec ticket using Herdr and Pi agents on a named worker node.
- [project-context-pack](project-context-pack/SKILL.md) — Use when the user wants a bounded repo context pack, project map, codebase index, or cached memory file so later work uses fd/rg/tree-sitter/LSP instead of repeated browsing.
- [recipe-diagrams](recipe-diagrams/SKILL.md) — Recipe diagrams: convert any recipe into a high-resolution Cooking for Engineers-style PNG process-flow table with aligned ingredient streams, preparation branches, joins, temperatures, timings, and finish steps. Use when the user asks for a recipe diagram.
- [security-audit](security-audit/SKILL.md) — Comprehensive security and correctness audit of a branch's changes. Use for deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.