القائمة
Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when creating executable /tmp Pi task harnesses for ambiguous or high-risk coding work. Builds contract, prompts, validation, logs, and enforcement rules.
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
Use when creating or modifying Pi extensions, built-in extension wiring, prompt shims, package scaffolds, package READMEs, or packages/pi-* implementation in this monorepo.
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
| name | execute-harness |
| description | Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation. |
| compatibility | Requires my-pi or Pi with the pi-harness extension tools enabled. |
Run the task through an existing my-pi harness. The harness is the execution contract.
harness.json, SYSTEM.md, TASK.md, and status.json
before editing.harness_update with status: running and the current phase.team tool is available and you are the team lead, create
or reuse a team, create/claim a task for the harness, and use one
member_spawn executor with mutating: true for file-editing
work. Default to the contract cwd; use workspace_mode: worktree
only when the user asks for isolation or the plan covers setup,
runtime state, merge, and cleanup ownership.harness.json,
SYSTEM.md, TASK.md, and status.json, execute only inside the
contract, run validate.sh and review.sh, update harness
evidence, and report changed files plus risks. If using a worktree,
set HARNESS_CWD to that worktree for validation and review.allowed_paths; do not fight
enforcement.harness_update, including team status and remaining risks when
known.<harness_dir>/validate.sh.<harness_dir>/review.sh from the execution workspace. If
using a linked worktree, run it from that worktree or set
HARNESS_CWD to the worktree path.<harness_dir>/OUTCOME.md or <harness_dir>/outcome.json
for changed files, baseline ignored files, validation evidence,
team status, and risks.completed only when validation passes and no escalation
rule applies; otherwise mark failed with evidence.