📝 docs: add "Update from External Sources" page to Playbook Maintenance

[cteyton]

Adds documentation explaining how teams can use AI agent skills and MCP
servers to automatically mine external sources (GitHub PRs, Slack, Jira,
GitLab MRs, Confluence, Notion) and feed findings into the playbook as
change proposals. Points to the demo-use-case-skills repository for
implementation details and example skills.

Co-Authored-By: Claude noreply@anthropic.com

https://claude.ai/code/session_01Pzq6KmeZD74kfkzumYNy5B

[greptile-apps]

Greptile Summary

This PR adds a new "Update from External Sources" documentation page to the Playbook Maintenance section, explaining how teams can automate playbook updates by mining GitHub PRs, Slack, Jira, GitLab MRs, Confluence, and Notion via AI agent skills and MCP servers. It also promotes Change Proposals out of private beta by removing the beta callout from change-proposals.mdx.

• New page is well-structured, clearly describes the three-stage pipeline (Fetch → Classify → Update), and correctly links to the demo-use-case-skills repository for implementation details.
• The private beta <Info> callout removal from change-proposals.mdx appears intentional and consistent with the new page treating the feature as generally available.
• Navigation registration in docs.json is correct.
• The MCP server links for Jira/Confluence (src/atlassian) and Notion (src/notion) inside the modelcontextprotocol/servers repository could not be confirmed to exist; the three other linked paths (src/github, src/slack, src/gitlab) were verified as live. These should be validated before merge to avoid dead links in documentation.

Confidence Score: 4/5

• Safe to merge with low risk — documentation-only change with one link accuracy concern to verify.
• All changes are documentation only with no impact on application logic. The content is accurate and well-written. The one open question (whether src/atlassian and src/notion paths are live in the official MCP servers repo) is low-stakes but worth verifying before publish to avoid dead links for users.
• apps/doc/playbook-maintenance/update-from-external-sources.mdx — verify the Atlassian and Notion MCP server link paths are live.

Important Files Changed

Filename	Overview
apps/doc/playbook-maintenance/update-from-external-sources.mdx	New documentation page explaining how to mine external sources (GitHub, Slack, Jira, GitLab, Confluence, Notion) via MCP servers and create change proposals. Well-structured with a clear pipeline description, but two of the six linked MCP servers (Atlassian, Notion) could not be confirmed to exist at the linked paths in the official modelcontextprotocol/servers repository.
apps/doc/playbook-maintenance/change-proposals.mdx	Intentionally removes the private beta callout, signalling Change Proposals has graduated to general availability. No other content changes.
apps/doc/docs.json	Correctly adds the new update-from-external-sources page to the Playbook Maintenance navigation group. No issues.

Sequence Diagram

sequenceDiagram
    participant Source as External Source
    participant MCP as MCP Server
    participant Agent as AI Agent
    participant Skill as packmind-update-playbook
    participant Packmind as Packmind

    Agent->>MCP: Fetch data
    MCP->>Source: Query API
    Source-->>MCP: Raw data
    MCP-->>Agent: Structured results
    Agent->>Agent: Classify findings
    Agent->>Skill: Hand off relevant findings
    Skill->>Packmind: Submit Change Proposals
    Packmind-->>Skill: Proposals confirmed
    Note over Packmind: Team reviews and approves proposals in UI

Loading

_{Last reviewed commit: e646cac}

[greptile-apps]

Missing Private Beta disclaimer for Change Proposals

The entire workflow described in this page culminates in submitting Change Proposals via the packmind-update-playbook skill. However, change-proposals.mdx prominently displays:

"Change Proposals is currently in private beta. Contact Packmind to get access to this feature."

The new page makes no mention of this restriction. A user who sets up the full MCP pipeline (configuring MCP servers, writing or copying skills, wiring up CI) will only discover they can't actually complete the workflow when they reach the Change Proposals step and lack access.

Consider adding an <Info> or <Note> callout near the top of the page — ideally right below the intro paragraph or within the "How It Works" section — referencing the private beta status, for example:

<Note>
  The **Update** step relies on [Change Proposals](/playbook-maintenance/change-proposals),
  which is currently in **private beta**. Contact Packmind to get access before
  setting up this workflow.
</Note>

[greptile-apps]

Inconsistent MCP server label for Jira vs. Confluence

Both the Jira and Confluence rows link to the exact same URL (/src/atlassian), which is correct — they share the Atlassian MCP server. However, the Jira row labels the link "Jira MCP" while the Confluence row labels it "Atlassian MCP". This asymmetry may confuse users into thinking they need different servers.

Consider aligning the label so users understand they are the same server:

Suggested change

	| **Jira Issues** | Resolved issues and their comments | [Jira MCP](https://github.com/modelcontextprotocol/servers/tree/main/src/atlassian) |
	| **GitLab MR Comments** | Review comments from merged merge requests | [GitLab MCP](https://github.com/modelcontextprotocol/servers/tree/main/src/gitlab) |
	| **Jira Issues** | Resolved issues and their comments | [Atlassian MCP](https://github.com/modelcontextprotocol/servers/tree/main/src/atlassian) |
	| **GitLab MR Comments** | Review comments from merged merge requests | [GitLab MCP](https://github.com/modelcontextprotocol/servers/tree/main/src/gitlab) |

[greptile-apps]

Unconfirmed MCP server paths for Atlassian and Notion

The Jira and Confluence rows both link to src/atlassian, and the Notion row links to src/notion inside the modelcontextprotocol/servers GitHub repository. Research of that repository confirms src/github, src/slack, and src/gitlab exist as actively-maintained reference servers — but src/atlassian and src/notion could not be confirmed to exist there.

The repository README now explicitly states it is "dedicated to housing just the small number of reference servers maintained by the MCP steering group", suggesting many community-contributed servers (including Atlassian and Notion) may have been removed or never merged.

If those paths are dead links, users following the documentation will hit 404s when trying to set up the Jira, Confluence, or Notion integrations. Please verify those paths are still live, and if not, update them to point to the correct upstream packages or community repositories.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud