atpm-harvest

To preserve Slack discussions before deletion, you harvest institutional knowledge into structured Confluence pages. This process extracts key decisions and context from ephemeral sources like Slack channels and publishes them as permanent references.

The best way to extract institutional knowledge from Google Docs and meeting transcripts is to use a harvesting process that identifies key topics, generates a manifest for approval, and then publishes the structured content directly to Confluence.

Yes, you can automatically publish harvested knowledge from Slack to Confluence. The workflow retrieves data using Slack MCP and Atlassian MCP, structures it, and publishes it as Confluence pages after user approval at designated checkpoints.

Yes, you need Glean and Jira MCP along with Slack MCP and Atlassian MCP to harvest institutional knowledge into Confluence. These dependencies enable deep discovery and data retrieval across platforms like Slack, Google Docs, and Jira.

Manifest generation for knowledge harvesting works by identifying and organizing topics from sources like Slack and Google Docs into a list. This manifest requires your review and approval before the actual content extraction and publishing to Confluence begins.

You should not use automated knowledge extraction for Confluence when source materials lack clear structure or context, as the process relies on identifying coherent topics from Slack, Google Docs, and transcripts to generate accurate manifests and useful pages.