メニュー
Use when changing Foreman's Node/Pi worker bridge, detached worker config/env, Pi SDK sessions, custom tools, tool policy, observability, worker terminal events, or sandboxed Pi resource paths.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | foreman-worker-pi-sdk |
| description | Use when changing Foreman's Node/Pi worker bridge, detached worker config/env, Pi SDK sessions, custom tools, tool policy, observability, worker terminal events, or sandboxed Pi resource paths. |
Use this skill for changes in src/orchestrator/dispatcher.ts, src/orchestrator/agent-worker.ts, src/orchestrator/pi-sdk-runner.ts, src/orchestrator/pi-sdk-tools.ts, packages/foreman-pi-extensions/**, or worker env/config surfaces.
~/.foreman/tmp/worker-<runId>.json, spawns a detached worker with cwd = worktreePath, strips CLAUDECODE, removes DATABASE_URL, and propagates FOREMAN_VCS_BACKEND.runPhaseSession() builds guarded built-in tools, custom Foreman tools, tool policy, observability, and in-memory Pi sessions.allowedTools controls built-in tools; custom Foreman tools (send_mail, mail_read, mail_send, phase_handoff, artifact_write, validation_result, task_block, progress_update, ask_operator, abort_phase, needs_retry, safe_command_run, VCS/PR helpers) have their own flow and policy checks.FOREMAN_PI_EXTENSIONS mode disables user skills and prompt templates; Foreman must explicitly pass bundled skill paths through additionalSkillPaths.getSandboxedPiResourcePaths() through a shared list, not hardcoded one-by-one.src/orchestrator/__tests__/pi-sdk-runner.test.ts for resource path/sandbox changes.Use when a Foreman change may affect documentation, commands, workflows, prompts, setup, troubleshooting, operator expectations, or skill inventory/package behavior.
Use when changing Foreman's Elixir/OTP backend under packages/foreman_server: event store, projections, scheduler, run/phase actors, worker protocol, PR/VCS reconciliation, operations, auth, or storage/test isolation.
Use when a Foreman run appears stuck, has missing artifacts, stale projections, failed PR gates, confusing inbox/debug output, or potentially missing phase reports.
Use when deciding between Foreman retry, reset, doctor --fix, worktree clean, abandon, or clean-state for failed/stuck/obsolete runs, branches, worktrees, or PRs.
Use when changing Foreman's Git/Jujutsu support, VcsBackend abstraction, worktree/workspace handling, finalize/rebase/merge/push commands, or workflow/project VCS configuration.
Use when editing or diagnosing Foreman workflow YAML, bundled prompts, pipeline executor behavior, phase artifacts, retries, command/bash/builtin phases, PR gates, or stale runtime prompt/workflow copies.