菜单
Use when implementing orchestration-driven service-oriented architecture: central workflow orchestration across services, explicit process models, compensations, service contracts, long-running transactions, and governance boundaries.
用 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 | orchestration-driven-soa |
| description | Use when implementing orchestration-driven service-oriented architecture: central workflow orchestration across services, explicit process models, compensations, service contracts, long-running transactions, and governance boundaries. |
Use this skill when a central process coordinator is the clearest way to manage cross-service workflows.
Use for long-running business processes, compliance-heavy flows, and integrations where visibility and control matter more than local autonomy. Avoid when simple choreography is sufficient or a central orchestrator would become a god service.
graphify-out/GRAPH_REPORT.md.graphify query "orchestration driven service oriented architecture workflow compensation".codebase/workflows/
<workflow>/
states
orchestrator
participants
compensations
tests/
codebase/services/*/contract
graphify explain "orchestrator" should show workflow-to-contract dependencies, not service internals.Return: workflow state model, participant contracts, orchestrator patch, compensation matrix, and verification evidence.