Recipes

Real-world workflows combining InteliG with the tools you already use. Copy, customize, ship.

What Recipes Are

Recipes are end-to-end workflows that combine InteliG's API with external tools — Slack, GitHub Actions, cron jobs, CI/CD pipelines. Playbooks automate InteliG. Recipes automate the loop between InteliG and everything else.

Daily Engineering Briefing

You're a hands-on CTO. You want a Slack message every morning telling you what your team shipped yesterday. No dashboards. No standups. Just a summary, waiting for you when you open Slack.

InteliG + Cognis + Slack

Scheduled daily via cron or GitHub Actions

  • Verify GitHub is connected — Call the InteliG API to confirm repositories are synced and data is flowing.
  • Ask Cognis — Send a prompt to the Cognis API: "What did my development team work on yesterday?" Cognis reasons across commits, PRs, and contributor activity to generate a summary.
  • Send to Slack — Take Cognis's response and post it to your Slack channel or DM via the Slack API.

Three API calls, zero human involvement. Schedule it with a cron job, a GitHub Action, or any automation tool. Your morning briefing builds itself.

Post-Deploy Impact Report

Every time you deploy to production, get an automatic impact report — what changed, who contributed, which initiatives were advanced, and whether quality metrics shifted.

InteliG + Code Intelligence + Cognis + Slack or Email

Triggered by CI/CD pipeline on deploy

  • Pull recent commits — Query Code Intelligence for commits merged since the last deploy.
  • Ask Cognis for impact analysis — "Summarize the impact of commits merged in the last 24 hours. Which initiatives were advanced? Any quality concerns?"
  • Deliver the report — Post to a #deployments Slack channel or email the engineering leadership team.

Wire it into your CI/CD pipeline as a post-deploy step. Every deploy gets context, not just a green checkmark.

Weekly Strategy Digest

A weekly summary of strategic alignment — which initiatives moved, where drift is happening, and what needs attention. Sent every Monday morning.

InteliG + Strategy + Cognis + Slack or Email

Scheduled weekly via cron or GitHub Actions

  • Pull strategy alignment data — Query the Strategy API for alignment scores and initiative activity over the past 7 days.
  • Ask Cognis for the narrative — "Give me a strategic alignment summary for the past week. What moved? Where is drift? What needs attention?"
  • Deliver to leadership — Post to a #strategy channel or email the exec team.

Your Monday morning strategy check, written by Cognis, delivered before the first meeting.

Sprint Kickoff Automation

Automate sprint setup end-to-end — create the sprint, link initiatives, generate AI intelligence, and notify the team. One trigger, everything ready.

InteliG + Strategy + Agent Playbook + Slack

Triggered manually or on a sprint cadence schedule

  • Run the Sprint Setup playbook — Create the sprint, set date range and goals, link initiatives.
  • Generate sprint intelligence — Trigger Cognis analysis for the new sprint window.
  • Notify the team — Post a sprint kickoff summary to Slack with linked initiatives, goals, and the AI-generated health assessment.

Combine the Sprint Setup playbook with a Slack notification step. Sprint planning goes from a 30-minute ceremony to a single command.

Build Your Own

Every recipe follows the same pattern: call InteliG's API, optionally ask Cognis to reason over the data, deliver the result somewhere useful. The building blocks:

  • InteliG API — Data and operations across all pillars. See the API Reference.
  • Cognis API — Natural language reasoning across your engineering data.
  • Agent Playbooks — Pre-built prompts for multi-step workflows. See Agent Intelligence.
  • Delivery — Slack, email, CI/CD comments, dashboards — wherever the result needs to go.

Pick the data source, pick the reasoning, pick the destination. That's a recipe.

Related

  • Agent Intelligence — Pre-built playbooks that power the InteliG steps in these recipes.
  • Cognis AI Engine — The reasoning engine behind every "Ask Cognis" step.
  • API Reference — Complete REST API documentation for building custom recipes.