CHATBOTS

Answer in Slack, then file a Linear doc-gap ticket on miss

Answers a Slack /askdocs question from ReadMe, and when no page adequately covers the topic.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack /askdocs slash command receivedSlack
  • ActionSearch ReadMe for candidate pagesReadMeReadMe
  • ActionJudge coverage and draft answer or gap briefOpenAI
  • LogicBranch on coverage verdict (answered vs gap)
  • ActionCreate Linear doc-gap ticket on missLinearLinear
  • OutputReply in Slack with answer and ticket noteSlack

What it does

Responds to a `/askdocs` Slack command using your ReadMe content, then closes the loop on missing documentation. When retrieval shows the question isn't well covered, it creates a Linear issue in your docs project containing the original question, the closest existing pages, and an LLM-drafted outline of what the new or updated doc should say.

When to use it

When you want your docs backlog to be driven by real unanswered questions instead of guesswork. Every time the bot can't confidently answer, your writers get a concrete, prioritized ticket.

How it works

  1. 1Slack sends the `/askdocs` payload to the webhook endpoint.
  2. 2ReadMe search returns the closest candidate pages.
  3. 3OpenAI judges coverage and writes either a cited answer or a doc-gap brief.
  4. 4A logic branch routes on the coverage verdict.
  5. 5On a miss, a Linear ticket is created with the question and suggested doc outline.
  6. 6The bot replies in Slack with the best-effort answer and notes the ticket.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect ReadMeAPI docs, changelog, auth.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.