菜单
Execute assigned delivery work when a prompt identifies this Pi session as an orch implementation, fix, review, or proof worker. Handles surgical changes, commits, read-only review, repository checks, and live proof in isolated worktrees.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/darjss/herdr-orchestrate --skill orch-implementation-worker命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Run a user-directed task through visible Pi workers with herdr-orchestrate.
Research and plan assigned work when a prompt identifies this Pi session as an orch exploration or research/plan worker. Handles evidence gathering, repository mapping, options, risks, and implementation briefs; exploration workers never edit or decide.
基于 SOC 职业分类
正在显示 SKILL.md
| name | orch-implementation-worker |
| description | Execute assigned delivery work when a prompt identifies this Pi session as an orch implementation, fix, review, or proof worker. Handles surgical changes, commits, read-only review, repository checks, and live proof in isolated worktrees. |
| license | MIT |
| compatibility | Requires Pi inside a herdr-orchestrate worker worktree. |
The assigned brief is authoritative. It names one role, the target base/commit, constraints, checks, and report path. Read repository instructions before acting.
Never inspect or modify another worker's worktree. Never expose or commit secrets when reproducing local environment setup.
This step is complete when the checked-out starting point and role constraints match the brief; otherwise report blocked.
Implement only the acceptance criteria. Follow existing patterns and remove only artifacts made obsolete by your change. Run repository-prescribed format, lint, type, build, and real-path validation; do not invent unit or integration tests when repository policy forbids them. Commit the coherent result. Push or open a PR only when the brief asks.
Inspect the target change for correctness, regressions, security, maintainability, requirement coverage, and missing validation. Every actionable finding needs severity, evidence (file:line when possible), impact, and a concrete requested fix. End findings with review-verdict: approved or review-verdict: changes-requested before the orch marker.
Use the real interface: browser for frontend behavior, actual CLI for terminal behavior, and actual HTTP/API calls for backend behavior. Record the exact action and observed result. A build alone is not live proof.
This step is complete when every acceptance criterion is mapped to a concrete artifact, check, finding, or observed result; uncertainty is a blocker, not a pass.
Follow ../references/worker-report.md. Authors must include branch and commit SHA. Reviewers must include target/base and verdict. Proof workers must include the exact live path and observation.
This step is complete only after the report exists at the exact orch path and ends with one valid orch-verdict marker.
