菜单
Use when authoring an AgentWorkforce persona's sidecar fields (`claudeMd` / `claudeMdContent` / `agentsMd` / `agentsMdContent`) — covers the silent-footgun path-vs-inline distinction the dry-run does NOT catch, which form to pick for local vs built-in personas, and `*Mode` (overwrite vs extend)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use before auto-merging any PR in an autonomous run, and between consecutive merges that touch overlapping code. Covers the per-PR auto-merge bar (live CI verification, substantive review by area, bot-finding stale-vs-actionable triage) and the cross-PR composition discipline (serialize through green main, rebase + re-CI between merges, dormant-safety audit, force-reset over half-merged commits).
Use at the start of every autonomous, multi-PR, cutover-class delegated run. Authors the binding contract between operator and agent — the gates, the flip mechanism, the rollback triggers, the standing constraints, and the explicit escalate-to-human conditions — and surfaces it to the operator for explicit grant of (a) auto-merge authority, (b) flip-the-switch authority, (c) swarm-blockers authority. No autonomous work begins until the contract is acknowledged.
Use when designing or executing a cutover-class change (migration, ingestion path swap, provider relink, flag enablement). Encodes the dark-launch + single-switch flip pattern, the refusal to flip on amber, and the pre-authorized rollback procedure — the canonical way to make irreversible-feeling infra changes reversible-feeling.
Use when a fix has failed two consecutive times for the same symptom. Encodes the discipline that the third action must be a temporary diagnostic (a /_diag endpoint, an enriched structured log, a runtime-captured snapshot) rather than another fix attempt. Also covers the discipline for removing those diagnostics once the real root cause is in.
Use during an autonomous run to (a) dispatch supporting codex-impl + claude-review agent pairs against hard blockers when the orchestrator cannot make progress alone, and (b) maintain the live RED / GREEN gate scoreboard the orchestrator reads to authorize the flip. Encodes the file-based reporting convention that keeps the channel readable.
Use when a single gate would require deep proof across a large set (44 models × 10 providers; 60+ resources; every region; every plan tier). Splits the acceptance into tier-1 (deep proof on high-volume / high-fidelity slice) and tier-2 (smoke proof on low-volume tail), documents the explicit accepted trade-off, and preserves safety through dormant-default + per-item enable + rollback.
| name | persona-sidecars |
| description | Use when authoring an AgentWorkforce persona's sidecar fields (`claudeMd` / `claudeMdContent` / `agentsMd` / `agentsMdContent`) — covers the silent-footgun path-vs-inline distinction the dry-run does NOT catch, which form to pick for local vs built-in personas, and `*Mode` (overwrite vs extend) |
You are advising an author writing the sidecar fields on an AgentWorkforce persona spec. A persona's heavy operating spec belongs in a sidecar markdown file, not in systemPrompt. The harness auto-loads CLAUDE.md (claude) or AGENTS.md (codex / opencode) from the session cwd on startup, so the CLI stages the sidecar there before launch.
| Field | Type | What it holds |
|---|---|---|
claudeMd | path | Relative path (from the persona JSON's directory) to a sibling .md file |
claudeMdContent | string | Inline markdown body as a literal string |
agentsMd | path | Relative path to a sibling .md file |
agentsMdContent | string | Inline markdown body as a literal string |
claudeMd / claudeMdContent are claude-only. agentsMd / agentsMdContent are codex + opencode.
Pick ONE shape per persona:
"claudeMd": "./my-persona.md""claudeMdContent": "# My Persona\n\n..."Putting a file path string into a *MdContent field stores that path verbatim as the entire body of CLAUDE.md / AGENTS.md at session start. The agent's operating spec becomes one line of garbage that looks like a filename. The agent then has no idea what its job is.
The validator only checks that the field is a non-empty string, not whether the string is real markdown content. A persona with "claudeMdContent": "my-persona.md" will:
✓ sidecar: CLAUDE.md)my-persona.mdThis is one of the most expensive footguns in workforce because failure is silent.
.agentworkforce/workforce/personas/<id>.json in a user repo) typically use the path form. The .md sidecar lives next to the JSON; you can edit it as a real markdown file instead of escaping a long string into JSON./personas catalog) also use the path form — the catalog generator at packages/workload-router/scripts/generate-personas.mjs inlines the sibling .md into claudeMdContent / agentsMdContent at build time so the published package ships a single bundled spec.Both pairs accept an optional claudeMdMode / agentsMdMode of "overwrite" (default) or "extend". Use "extend" when the persona's spec should append to a user-supplied CLAUDE.md/AGENTS.md already in the cwd rather than replacing it.
.md file? → use claudeMd / agentsMd (path form).*Content field looks like a filename string (ends in .md, contains slashes, single line)? STOP — that's the wrong field. Move it to the *Md (path) field.*Md field is relative to the persona JSON's directory (not to the project root or session cwd)?