メニュー
Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.
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.
Bootstrap ls-lint filename rules for harness projects — seed naming.manifest.json, generate merge-safe .ls-lint.yml, and document bootstrap vs --force sync. Use during /harness-setup, when adding ls-lint to a repo, or when .ls-lint.yml is missing or out of date.
| name | harness-governor |
| description | Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages. |
harness-policy-violation, budget exhausted, or review-integrity blocks/harness-policy-status or session harness-policy-state.PolicyEngine + .pi/harness/policies/*.yaml (parent policy-gate, subprocess harness-subagent-governance). Disable with HARNESS_AGT_POLICY=0. Audit: .pi/harness/runs/<run_id>/agt-audit.jsonl.HARNESS_SENTRUX_REQUIRED=true (artifacts/sentrux-signal.yaml from /harness-run, not executor self-report)./harness-sentrux-steward + chair + formal decision record when material, then sentrux-rules-sync --force. Naming manifest changes → /harness-ls-lint-steward + chair, then ls-lint-rules-sync --force. CLI degradation after execute → fix paths or replan — do not tune manifest on a single noisy run.harness-sentrux-bootstrap.mjs --force or /harness-sentrux-sync; emit harness-architecture-changed. After naming edits: harness-ls-lint-bootstrap.mjs --force or /harness-ls-lint-sync; emit harness-naming-changed.node "$UP_PKG/.pi/scripts/harness-verify.mjs" before claiming release readiness (includes AGT policy doctor).When refining plans from noisy requirements:
plan-packet fields and testable checks.human_required or promotion is blocked, the orchestrator calls ask_user — do not guess scope.graphify query for architecture constraints before execute.HARNESS_BUDGET_ENFORCE off — token/debate caps are telemetry-only (harness-budget-telemetry, harness-budget-soft-limit). They do not block phases or debate lanes.planning-context.yaml), debate rounds, or approve_plan because of soft budget hints in the widget.HARNESS_BUDGET_ENFORCE=1 and HARNESS_BUDGET_HARD_STOP / HARNESS_DEBATE_HARD_STOP.submit_* tools; parent verifies with harness_artifact_ready, not JSON parsing from finalOutput.write_harness_yaml is for merges (research-brief.yaml, plan shell) — not subagent payloads.