Turns a Slack request and an approved Google document into a cited answer, appends only the reviewed update, responds in-channel, and preserves both provider receipts.
Designed for
Operations and product teams maintaining living internal knowledge
Operating goal
Answer one team question from approved sources and publish the reviewed knowledge update with durable proof.
3 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 4 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 2 harnesses before production use.
Reads the current request and source document without widening scope.
Long-context retrieval model
Creates a concise cited answer and reusable document update.
High-quality writing model
Appends the reviewed update and posts the cited answer after approval.
Structured output model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for Knowledge Operations Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
Read the selected Slack context and Google document and identify evidence for the question.
Prepare the exact document append and channel response with citations.
Append the reviewed text and post the cited Slack response.
Open it in Codelit, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowReads one release channel, prepares a concise owner-ready update, pauses on the exact message, posts it once, and returns Slack delivery proof.
Reads one source page, distills a reusable decision or runbook update, pauses on the exact page content, creates a child page once, and returns Notion proof.
Turn an inbox request into a researched draft, calendar handoff, and updated operating record. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.