SLACK API // YOUR APPS

Select the existing app.

Open Slack apps ↗

01.1
Open Slack API → Your Apps.
Sign in at api.slack.com/apps ↗.
01.2
Select the app and workspace.
Open the app that should run Documentation Agent. Confirm the workspace before changing its manifest.

SLACK APP // APP MANIFEST

Apply the recipe manifest.

The name and description are already set for Documentation Agent.

02.1
Open Features → App Manifest.
Choose App Manifest and select the JSON tab.
02.2
Back up the current manifest.
Copy the existing JSON to a secure working document before changing it so workspace-specific settings can be preserved or restored.
02.3
Replace or merge the configuration.
Copy the manifest below. Merge it when the existing app has settings your team still needs.
02.4
Save the manifest.
Review Slack's change summary, then click Save Changes.

JSON MANIFEST

{
  "display_information": {
    "name": "AgentBarn_Recipe_Documentation",
    "description": "Turns merged pull requests and linked Jira work into Confluence updates, changelog entries, and a weekly digest.",
    "background_color": "#CC4400"
  },
  "features": {
    "app_home": {
      "home_tab_enabled": false,
      "messages_tab_enabled": true,
      "messages_tab_read_only_enabled": false
    },
    "bot_user": {
      "display_name": "AgentBarn_Recipe_Documentation",
      "always_online": true
    }
  },
  "oauth_config": {
    "scopes": {
      "bot": [
        "app_mentions:read",
        "canvases:read",
        "canvases:write",
        "channels:history",
        "channels:join",
        "channels:read",
        "chat:write",
        "chat:write.customize",
        "chat:write.public",
        "emoji:read",
        "files:read",
        "files:write",
        "groups:history",
        "groups:read",
        "im:history",
        "im:read",
        "im:write",
        "mpim:history",
        "mpim:read",
        "mpim:write",
        "pins:read",
        "pins:write",
        "reactions:read",
        "reactions:write",
        "search:read.users",
        "users:read",
        "users:read.email"
      ]
    },
    "pkce_enabled": false
  },
  "settings": {
    "event_subscriptions": {
      "bot_events": [
        "app_mention",
        "channel_rename",
        "member_joined_channel",
        "member_left_channel",
        "message.channels",
        "message.groups",
        "message.im",
        "message.mpim",
        "pin_added",
        "pin_removed",
        "reaction_added",
        "reaction_removed"
      ]
    },
    "interactivity": {
      "is_enabled": true
    },
    "org_deploy_enabled": false,
    "socket_mode_enabled": true,
    "token_rotation_enabled": false,
    "is_mcp_enabled": false
  }
}

SLACK APP // SOCKET MODE

Create the app-level token.

03.1
Open Basic Information → App-Level Tokens.
Click Generate Token and Scopes.
Generate Token and Scopes.
03.2
Name the token and add the scope.
Use AgentBarn_Recipe_Documentation, add connections:write, and click Generate.
Name → connections:write → Generate.
03.3
Copy the xapp- value.
Keep it ready for the Agent Barn App-level token field.
The value is blurred; use Copy.

SLACK APP // WORKSPACE INSTALL

Install the app and copy the bot token.

04.1
Open Install App.
Click Install to [your workspace].
Install App → Install to workspace.
04.2
Review the workspace and permissions.
Confirm the workspace, review the requested access, and choose Allow.
Confirm workspace → review access → Allow.
04.3
Copy the Bot User OAuth Token.
In Installed App Settings → OAuth Tokens, copy the xoxb- value.
Bot User OAuth Token → Copy.

AGENT BARN // SLACK CREDENTIALS

Connect both Slack values.

APP-LEVEL TOKENxapp-…

Paste the value from App-Level Tokens.

BOT TOKENxoxb-…

Paste the Bot User OAuth Token.

05.1
Enter the values in their matching fields.
Paste the complete xapp- and xoxb- values, then save.
05.2
Confirm the connected app.
Check that Agent Barn resolves the expected Slack app and workspace.

AGENT BARN // SETTINGS

Configure the agent.

06.1
Name the agent.
Use AgentBarn_Recipe, or another role-specific name your team will recognize.
06.2
Select and test the model.
Choose an available model, then run one representative Documentation Agent task before connecting broader access.
06.3
Choose command approval.
Auto · Manual · Off
Auto
Runs low-risk commands automatically.
Manual
Asks before every command.
Off
Runs without approval prompts.
06.4
Choose response detail.
Verbose · Concise
Verbose
Shows progress while working.
Concise
Returns the result without step narration.
06.5
Configure the recipe trigger and workflow.

Trigger: A pull request is merged or a scheduled digest is due.
1. Detect change. Read the merged pull request and linked Jira context.
2. Draft update. Prepare a Confluence update or changelog entry.
3. Check scope. Keep the update within configured sources and policies.
4. Share digest. Post the prepared summary to the allowed Slack channel.
06.6

Apply the recipe requirements and review rule.

Template
Documentation agent instructions and output format.
Skills
GitHub or Bitbucket plus Jira and Confluence access.
Channels
A permitted Slack channel for digests and questions.

Review rule
Review generated documentation before treating it as the final record of a product or engineering decision.

SLACK // ACCESS

Set Slack access rules.

07.1
Choose channel access.
Allowlist · Open
Allowlist
Respond only in channels you add.
Open
Respond in any channel the app can reach.
07.2
Choose direct-message access.
Off · Allowlist · Open
Off
Ignore direct messages.
Allowlist
Reply only to approved people.
Open
Reply to anyone who can reach the app.
07.3
Add and test the intended destinations.
Invite the Slack app to each allowed channel, add the same channels or people in Agent Barn, and send one test request.

AGENT BARN // INTEGRATIONS

Connect the skills for Documentation Agent.

CHOOSE ONE

GitHub or Bitbucket

Read merged pull requests, diffs, labels, and linked engineering context.

Credential: A GitHub App or Bitbucket access token scoped to the repositories this recipe documents.
Permissions: Repository metadata: read · Pull requests and diffs: read · Comments: write only if the workflow posts review notes

Choose the provider that owns the source repositories.
Limit installation or token access to the repositories in scope.
Subscribe only to merged pull-request events and any explicitly required update events.

REQUIRED

Jira and Confluence

Read linked Jira work and create or update documentation and changelog content in approved Confluence spaces.

Credential: One Atlassian account email and site URL, with an API credential verified for the required Jira and Confluence operations.
Permissions: Jira projects and linked issues: read · Confluence target spaces: view · Confluence pages: add or update where required · Comments: add only if the recipe uses review comments

Identify the Jira projects referenced by the source repositories.
Identify the destination Confluence spaces and page hierarchy.
Use an account whose Jira and Confluence access is limited to those locations.
Validate Jira reads and Confluence writes in non-production test locations.

08.1
Select only this recipe’s integrations.
Keep required skills. Where a card says “choose one,” connect the provider that owns the relevant data.
08.A1
Atlassian // Copy the site origin.
Use the address through .atlassian.net; omit Jira project and Confluence space paths.
Site URL
08.A2
Atlassian // Open API tokens.
Open Profile → Account settings → Security → Create and manage API tokens.
Account settings
API token manager
08.A3
Atlassian // Create the matching token type.
Choose standard or scoped, use the same authentication type in Agent Barn, add a name and expiration, then copy the value.
Choose token type
Name · expiration · create
08.A4
Atlassian // Complete the credential.
SITE URL
Atlassian site origin.
AUTHENTICATION TYPE
Match the token type.
EMAIL
Atlassian account email.
API TOKEN
Copied token value.
Jira and Confluence can use the same credential when the account and token cover both products.
08.A5
Atlassian // Validate the product boundary.
Test one permitted Jira project or Confluence space for every connected product, then confirm a location outside the configured boundary remains unavailable.
08.S1
Source control // Choose GitHub or Bitbucket.
Read merged pull requests, diffs, labels, and linked engineering context.
08.G1
GitHub // Create a Classic PAT.
Open Personal access tokens ↗, choose Tokens (classic) → Generate new token, set a note and expiration, then select repo, read:org, and read:user.
08.G2
GitHub // Copy and map the credential.
The token is blurred; use the copy control.
Owner / Org is before the slash.
08.G3
GitHub // Restrict and validate repositories.
Add every permitted repository explicitly. The Classic PAT repo scope is broad, so test one repository in the configured list and confirm a repository outside the configured list remains unavailable.
08.B1
Bitbucket // Create a scoped API token.
Open Account settings → Security → Create and manage API tokens, choose Bitbucket, and add read access for user, workspace, repository, and pull requests.
WORKSPACE
Workspace ID.
REPOSITORIES
Permitted names.
EMAIL
Atlassian account email.
API TOKEN
Bitbucket-scoped value.
08.B2
Bitbucket // Restrict and validate repositories.
Add every permitted repository explicitly. Test one repository in the list and confirm a repository outside the configured list remains unavailable; verify pull-request write access only when this recipe posts review comments.
08.Z
Test every selected integration.
Run one expected action for each skill and confirm resources outside the selected boundary remain unavailable.

FINAL CHECK

Verify the complete recipe.

The existing Slack app connects with both Slack values.
The app responds in an allowed channel.
A destination outside the selected access rule receives no response.
Each required integration completes one representative task.
The command-approval and response-detail choices behave as selected.
The configured trigger runs: A pull request is merged or a scheduled digest is due.
The result follows Detect change → Draft update → Check scope → Share digest.
The review rule is applied: Review generated documentation before treating it as the final record of a product or engineering decision.

RECIPE PATH COMPLETE

Documentation Agent is ready for a controlled pilot.

Start with a narrow audience and reversible work, then widen access after observing representative tasks.

Return to recipes →

Set up Documentation Agent with an existing Slack app.

Open Slack API → Your Apps.

Select the app and workspace.

Open Features → App Manifest.

Back up the current manifest.

Replace or merge the configuration.

Save the manifest.

Open Basic Information → App-Level Tokens.

Name the token and add the scope.

Copy the xapp- value.

Open Install App.

Review the workspace and permissions.

Copy the Bot User OAuth Token.

Enter the values in their matching fields.

Confirm the connected app.

Name the agent.

Select and test the model.

Choose command approval.

Choose response detail.

Configure the recipe trigger and workflow.

Apply the recipe requirements and review rule.

Choose channel access.

Choose direct-message access.

Add and test the intended destinations.

GitHub or Bitbucket

Jira and Confluence

Select only this recipe’s integrations.

Atlassian // Copy the site origin.

Atlassian // Open API tokens.

Atlassian // Create the matching token type.

Atlassian // Complete the credential.

Atlassian // Validate the product boundary.

Source control // Choose GitHub or Bitbucket.

GitHub // Create a Classic PAT.

GitHub // Copy and map the credential.

GitHub // Restrict and validate repositories.

Bitbucket // Create a scoped API token.

Bitbucket // Restrict and validate repositories.

Test every selected integration.

Documentation Agent is ready for a controlled pilot.

Copy the `xapp-` value.