菜单
Orchestrate ultimate-pi harness phases with the native `subagent` tool (isolated `pi --mode json` subprocesses). Use for plan/execute/evaluate pipelines, L4 verification, optional planning-context, and debate prep.
用 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-orchestration |
| description | Orchestrate ultimate-pi harness phases with the native `subagent` tool (isolated `pi --mode json` subprocesses). Use for plan/execute/evaluate pipelines, L4 verification, optional planning-context, and debate prep. |
Follow the orchestration rules and phase sequence in this skill directly.
tasks only when outputs are independent inputs to a later merge (implementation ∥ stack). Never parallelize debate lanes or decompose ∥ hypothesis.planning-context subagent, 1 executor, 1 debate agent per subagent call.approve_plan, create_plan, submit_* via source_path, merge_harness_yaml, harness_synthesize_repair_brief./harness-* prompts parse args, call subagent, run ask_user, write policy-gated artifacts. Phase logic lives in .pi/agents/harness/*.md and .pi/agents/harness/planning/*.md.
Every spawn includes HarnessSpawnContext JSON in the task text (subprocess agents do not get [HarnessActivePlan] injection). Use agentScope: "both" so package agents under $UP_PKG/.pi/agents/** resolve.
Harness subprocesses load harness-subagent-submit (PI_HARNESS_SUBPROCESS=1, HARNESS_RUN_ID, HARNESS_RUN_DIR). Agents must call their scoped submit_* tool before exit; parent gates use harness_artifact_ready.
tasks — Phase 3.5 research only (when using subprocesses).timeoutMs unless the user requests a cap.| Command | agent |
|---|---|
/harness-plan | Parent: planning context (tools) → decompose → hypothesis → Phase 3.5 artifacts → PlanPacket → eligibility + Review Gate → approve_plan + create_plan |
/harness-run | harness/running/executor (single worker) |
/harness-review | Parent verify → evaluator benchmark → evaluator verdict → adversary → optional tie-breaker |
/harness-eval | Deprecated → /harness-review |
/harness-critic | Deprecated → /harness-review |
/harness-auto | plan per /harness-plan; --quick skips adversary + tie-breaker in review |
Spawn harness/reviewing/evaluator / harness/reviewing/adversary via subagent in the same parent session. review-integrity allows subagent when agent is in the review set.
| Role | ask_user |
|---|---|
| Parent orchestrator | Yes (plan clarification, approve_plan, router tune) |
harness/planning/* | No — human_required in output if stuck |
harness/reviewing/evaluator, harness/reviewing/adversary, harness/reviewing/tie-breaker | human_required in subprocess JSON |
harness/running/executor | No — parent handles governance |
/harness-plan)Phase 1 — planning context (parent default):
graphify query, sg -p, ccc search, and reads as needed.artifacts/planning-context.yaml via write_harness_yaml.planning-context subagent when isolation helps.Phase 2 — sequential:
subagent decompose → gate decomposition.yaml
subagent hypothesis → gate hypothesis.yaml
Phase 3.5 — research artifacts required: parent inline and/or parallel implementation-researcher + stack-researcher (≤2).
Then execution-plan-author, DAG gate, debate eligibility, sequential debate rounds, approve_plan + create_plan.
.pi/harness/specs/harness-spawn-context.schema.jsonnode "$UP_PKG/.pi/scripts/harness-agents-manifest.mjs" --check