gitadmin
18ef02a331
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.
3.2 KiB
3.2 KiB
Engineering Skills
Daily code work.
User-invoked
- commit-staged — Commit staged files with a conventional commit message.
- grill-with-docs — Interview the user to sharpen a plan or design while creating ADRs and glossary docs.
- implement — Implement a piece of work from a spec or set of tickets.
- implement-isolation — Implement a piece of work from a spec or set of tickets in isolation.
- implement-isolation-tmux — Dispatch an isolated worktree agent to implement work from a PRD or issues.
- improve-codebase-architecture — Find and work through opportunities to deepen a codebase's architecture.
- orchestrate-herdr — 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.
- project-context-pack — Build a bounded project context pack for later agent work.
- recipe-diagrams — Convert recipes into high-resolution process-flow diagrams.
- setup-skills — Configure engineering skills, issue tracking, triage labels, and domain docs.
- to-spec — Turn the current conversation into a spec and publish it to the issue tracker.
- to-tickets — Break a plan or spec into tracer-bullet tickets with dependencies.
- triage — Triage issues and external PRs through the project workflow.
- wayfinder — Plan large work as decision tickets and resolve them step by step.
Model-invoked
- code-review — Review changes against repository standards and the originating specification.
- codebase-design — Design and improve deep module interfaces and seams.
- dual-review — Run parallel correctness/security and maintainability reviews of a branch diff, then synthesize findings.
- diagnosing-bugs — Diagnose hard bugs and performance regressions.
- domain-modeling — Build and sharpen a project's domain model.
- lsp-code-analysis — Navigate code and analyze it semantically with LSP.
- prototype — Build a throwaway prototype to answer a design question.
- research — Investigate a question using high-trust sources and capture the findings.
- resolving-merge-conflicts — Resolve an in-progress Git merge or rebase conflict.
- tdd — Use test-driven development for features, bugs, and integration tests.
- wizard — Generate an interactive wizard for steps only a human can perform.
- worktrees — Manage Git worktrees in a canonical repository root.
- write-discoverable-code — Write code agents and humans can find through plain-text search.