القائمة
Draft or refine harness artifact contracts under .pi/harness/specs. Use when defining PlanPacket, RunTrace, HarnessRunRecord, eval verdicts, or PostHog event schemas for ultimate-pi.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Commit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json. Use when the user asks to commit, when /harness-auto or harness run completion requires a commit, or before any git commit — never use raw git commit -m.
Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths.
Plan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.
Structured user decisions via ask_user for harness setup, planning, and governance forks. Use with /harness-setup, /harness-plan, harness-auto plan phase, and when agents emit human_required.
Deprecated — use harness-review skill and /harness-review for the full post-run gate. This file remains as a pointer for older prompts.
Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.
| name | harness-spec |
| description | Draft or refine harness artifact contracts under .pi/harness/specs. Use when defining PlanPacket, RunTrace, HarnessRunRecord, eval verdicts, or PostHog event schemas for ultimate-pi. |
.pi/harness/specs/README.md for versioning rules (contract_version, optional fields only for compatible changes)..pi/harness/specs/.node "$UP_PKG/.pi/scripts/harness-verify.mjs" (see .pi/scripts/README.md).@posthog/pi unchanged; harness events belong in harness-posthog-event.schema.json.