{
  "id": "workflow:developer-documentation-review",
  "_kind": "Workflow",
  "_file": "domain/workflows/workflows-technical-depth.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Developer Documentation Review",
    "description": "Structured review workflow ensuring that developer-facing documentation — API references,\nguides, tutorials, and changelogs — is accurate, complete, and consistent with each\nrelease. The documentation engineer audits recently changed APIs against published docs,\nidentifies gaps and outdated examples, and drafts updates. The tech lead reviews\ntechnical accuracy while a peer editor checks clarity and structure. Review feedback is\naddressed before the documentation is published alongside the corresponding release,\npreventing developer confusion from stale or missing content.\n",
    "workflowKind": "development",
    "triggerType": "event-driven",
    "typicalCadence": "per-release",
    "complexity": "moderate"
  },
  "outgoingEdges": [
    {
      "from": "workflow:developer-documentation-review",
      "to": "role:documentation-engineer",
      "kind": "involves_role"
    },
    {
      "from": "workflow:developer-documentation-review",
      "to": "role:tech-lead",
      "kind": "involves_role"
    },
    {
      "from": "workflow:developer-documentation-review",
      "to": "role:technical-writer",
      "kind": "involves_role"
    },
    {
      "from": "workflow:developer-documentation-review",
      "to": "role:backend-engineer",
      "kind": "involves_role"
    },
    {
      "from": "workflow:developer-documentation-review",
      "to": "domain:software-engineering",
      "kind": "applies_to_domain"
    }
  ],
  "incomingEdges": [
    {
      "from": "tool:tavily",
      "to": "workflow:developer-documentation-review",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "RAG retrieval can project related docs and external references into review workflows."
      }
    },
    {
      "from": "tool-server:mcp-docusaurus",
      "to": "workflow:developer-documentation-review",
      "kind": "supports_work",
      "attributes": {
        "confidence": "high",
        "evidence": "Docs source and build surfaces can be reviewed as a documentation workflow."
      }
    },
    {
      "from": "tool-server:mcp-confluence",
      "to": "workflow:developer-documentation-review",
      "kind": "supports_work",
      "attributes": {
        "confidence": "high",
        "evidence": "Docs review can project page changes, comments, and approvals from Confluence."
      }
    },
    {
      "from": "tool-server:mcp-tavily",
      "to": "workflow:developer-documentation-review",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "Search and retrieval support source discovery during documentation review."
      }
    },
    {
      "from": "tool-server:mcp-gitbook-candidate",
      "to": "workflow:developer-documentation-review",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "GitBook is a developer-docs publishing system relevant to review projections."
      }
    },
    {
      "from": "lib-process:technical-documentation--docs-audit",
      "to": "workflow:developer-documentation-review",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 0.7
      }
    },
    {
      "from": "lib-process:technical-documentation--docs-pr-workflow",
      "to": "workflow:developer-documentation-review",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 0.7
      }
    }
  ]
}