菜单
Use only when creating, resuming, inspecting, updating, completing, or writing artifacts for an authorized .workflow plan or audit run through the bundled Workflow MCP tools. It is an operations contract, not a reason to create workflow artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for an actual ready, non-draft GitLab merge request review, re-review, or approval decision when current discussions, diff, CI, scope, findings, and approval state must be checked. Do not trigger for casual MR discussion, draft/WIP work, GitHub PRs, or local code review.
Use at conversation start, after context recovery, and for non-trivial engineering work to select exactly one primary workflow path plus one task-wide assurance and verification budget. Loading this router does not create artifacts, launch agents, or activate every workflow module.
Use when an authorized, sufficiently clear change needs a durable decision-complete plan under .workflow because execution is multi-step, risky, resumable, or explicitly requested. Do not create a plan for fast local work or read-only discussion.
Use at conversation start, after compaction or context recovery, and before Agent Memory reads or writes to decide whether durable global or project knowledge can materially change the task. Keep startup reads focused, and do not mutate memory during read-only or no-edits work unless the user explicitly asks to remember something.
Use after intent routing only when unresolved requirements, product intent, architecture, constraints, or tradeoffs can materially change scope, risk, acceptance criteria, or user-visible behavior. Inspect discoverable facts first and avoid exhaustive questioning.
Use to execute an approved active .workflow plan with milestone state updates, scoped task ownership, compaction recovery, selective worktree delegation, and one integration path. Do not use for direct fast-path work without a durable plan.
| name | workflow-mcp |
| description | Use only when creating, resuming, inspecting, updating, completing, or writing artifacts for an authorized .workflow plan or audit run through the bundled Workflow MCP tools. It is an operations contract, not a reason to create workflow artifacts. |
Use the matching MCP tool for deterministic .workflow/ state and artifact operations whenever it is available. This is the normal path, not a preference. MCP does not generate substantive content, launch agents, merge worktrees, run verification, or replace judgment.
.workflow/ is the default artifact root. When workflow_status reports a
configured root from mcp-config.yml, treat the reported path as authoritative;
do not assume or manually recreate the default directory.
workflow_statusworkflow_plan_create, workflow_plan_update, workflow_plan_complete, workflow_plan_artifact_writeworkflow_plan_commitment_propose, workflow_plan_commitment_confirmworkflow_audit_create, workflow_audit_update, workflow_audit_complete, workflow_audit_artifact_writeworkflow_handoff_writeworkflow_findings_normalizeLoading this skill never authorizes a new plan/audit. The active primary workflow and action boundary decide whether artifacts may exist.
workspace_root when cwd may be a parent or sibling workspace.workflow_status at start/resume, after compaction, or when active state is uncertain; do not call it before every phase merely for reassurance.workflow_plan_create or workflow_audit_create. Existing unfinished work uses the matching update tool. Do not reopen completed runs without an explicit request.content or json.workflow_plan_complete or workflow_audit_complete; phase-only updates do not clear the root active pointer.Commitment reflection is platform-neutral state and same-model judgment. Use the propose/confirm tools for material plans before execution and after material scope divergence. A Codex Stop hook may enforce missing state, but skills and MCP remain complete without it; Claude Code and other clients must never be instructed to find or wait for that hook.
Before creating artifacts in a git repository, ensure .workflow/ is ignored unless explicitly versioned.
Use the operation names and payload fields exposed by the live tool schema. For task status, use upsert_task with a full task object or complete_task with task_id. For chunks, use lifecycle operations rather than inventing setters.
If a call fails with an unsupported operation, schema, payload, or validation error, read the nearest supported-operation hint, correct the same MCP call, and retry. Do not switch to manual files while the matching tool remains available.
Read references/operations.md only when creating a run, manipulating chunks/handoffs, recovering an operation error, or diagnosing installed-package drift.
Manual .workflow/ writes are fallback only when the matching MCP tool is unavailable. Preserve the same layout and state semantics and report the fallback.
Stop after the requested deterministic operation succeeds. Do not inspect unrelated artifacts or add workflow stages.