{
  "schema_version": "prompt-examples/v1",
  "skill": "spec-doc-review",
  "examples": [
    {
      "name": "authorized document review uses bounded personas",
      "user_intent": "用户要求审查 requirements、plan 或 task-pack 文档，并显式授权 subagents、parallel reviewers、delegated review 或 persona reviewer dispatch。",
      "expected_posture": "按文档类型和内容信号选择 personas；在 host capability 和 explicit dispatch authorization 同时存在时进行 bounded parallel dispatch，然后 synthesis findings。",
      "boundary_note": "spec-doc-review 是 workflow orchestrator，不是 agent type；不要把 workflow 自身丢给 subagent，也不要把直接调用 workflow 当作 Codex `spawn_agent` 授权。",
      "negative_signal": "缺少显式 dispatch authorization 时仍启动 subagents，或通过 Agent primitive 调用 spec-doc-review。",
      "context_snippets": ["Select Conditional Personas", "Dispatch Capability Gate"],
      "source_note": "existing prompt clause: Document Review workflow and Invocation Boundary",
      "id": "authorized-document-review-uses-bounded-personas",
      "coverage_tags": ["trigger"]
    },
    {
      "name": "dispatch unavailable or unauthorized falls back honestly",
      "user_intent": "运行环境没有 reviewer dispatch primitive、用户明确要求 no-agents/report-only，或 direct `spec-doc-review` 调用没有显式授权 Codex subagents / parallel reviewer work。",
      "expected_posture": "执行 single-agent report-only fallback，并清楚说明多 persona dispatch 未运行。",
      "boundary_note": "缺少 dispatch 不是跳过审查的理由，但不能声称 helper agents 已完成。",
      "negative_signal": "编造 persona agent 输出或把 unavailable dispatch 当成 review pass。",
      "context_snippets": ["dispatch_authorization_missing", "single-agent report-only fallback"],
      "source_note": "known failure mode: helper dispatch availability must be disclosed instead of simulated",
      "id": "dispatch-unavailable-or-unauthorized-falls-back-honestly",
      "coverage_tags": ["boundary", "failure"]
    },
    {
      "name": "findings need severity evidence and confidence",
      "user_intent": "审查产物需要 actionable findings，而不是泛泛建议。",
      "expected_posture": "findings 必须包含 severity、section、why_it_matters、confidence 和 evidence；低信心内容要降级或抑制。",
      "boundary_note": "reviewer 判断可以是语义的，但输出契约必须让 synthesis 能排序、过滤和呈现。",
      "negative_signal": "无 evidence 的结论、连续 confidence 值、或使用 high/medium/low 替代 P0-P3。",
      "context_snippets": ["findings schema", "confidence-first rubric"],
      "source_note": "existing prompt clause: subagent-template output-contract injects findings schema",
      "id": "findings-need-severity-evidence-and-confidence",
      "coverage_tags": ["trigger"]
    },
    {
      "name": "document review does not implement code",
      "user_intent": "用户要求审查一个 plan，review 发现可实施的修复方向。",
      "expected_posture": "输出 finding、safe_auto document fixes 或 Open Questions；需要代码执行时交给 work/code-review handoff。",
      "boundary_note": "doc-review 只拥有文档审查和允许的文档修复，不自动实施 plan code。",
      "negative_signal": "审查过程中顺手修改 source code 或运行 implementation tests。",
      "context_snippets": ["When Not To Use", "Downstream Consumers"],
      "source_note": "existing prompt clause: spec-doc-review is not for implementing fixes as a work run",
      "id": "document-review-does-not-implement-code",
      "coverage_tags": ["boundary"]
    },
    {
      "name": "runtime mirror confusion is high-risk",
      "user_intent": "文档建议直接修改 `.claude/`, `.codex/`, or `.agents/skills/` 来修复 workflow 行为。",
      "expected_posture": "将 source/runtime 混淆标为高风险 finding，并建议 source-first + runtime regeneration boundary。",
      "boundary_note": "review 不应认可手改 generated runtime mirror 作为 source-of-truth 修复。",
      "negative_signal": "把 runtime mirror diff 当作当前 contract 或 source evidence。",
      "context_snippets": ["generated runtime mirrors", "source-of-truth"],
      "source_note": "current source/runtime governance rule: AGENTS.md and thin governance contract",
      "id": "runtime-mirror-confusion-is-high-risk",
      "coverage_tags": ["boundary", "failure"]
    },
    {
      "name": "learning-capture recommendation is advisory and non-gating",
      "user_intent": "spec-doc-review 在 headless 模式发现可复用的 source/runtime 边界教训。",
      "expected_posture": "输出至多一行 advisory 行，指向 spec-compound，包含 learning candidate、证据路径、建议动作和用户选择记录方式。不自动运行 spec-compound，不自动写 docs/solutions/，不把 learning capture 作为 verdict input 或 review gate。",
      "boundary_note": "learning capture 永远不应成为阻断 review 完成的 gate，也不应在任何模式（interactive、headless、safe_auto）下自动执行 compound。",
      "negative_signal": "自动运行 spec-compound 或把 learning-capture recommendation 当作 P0/P1 finding 或 merge gate。",
      "context_snippets": ["Learning Capture Recommendation", "at most one advisory line", "Do not automatically run"],
      "source_note": "R4 / AE-04 — learning-capture advisory path",
      "id": "learning-capture-advisory-non-gating",
      "coverage_tags": ["boundary", "learning-capture"]
    }
  ],
  "source_refs": ["skills/spec-doc-review/SKILL.md"],
  "source_ref_authority": "source"
}