Playbook Index
Seed registry for reusable playbooks that have been formalized into the repo. New playbooks should be added here when they are created or materially updated.
Use Draft until a playbook has had at least one internal review and is ready to be treated as published.
| Name | Domain | Artifact type | Frequency | Path | When to use | Owner | Status |
|---|---|---|---|---|---|---|---|
| Add New User to Azure + AI Resources | Engineering | Playbook | Per new member | add-user-azure-ai-resources-playbook.md | Use when provisioning Azure and AI tool access for new team members: role classification, Azure OpenAI credentials, future Azure AD user creation commands, and role-based access matrix. | Platform | Draft |
| AWS CLI + Okta SSO profile setup (deterministic) | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/aws-cli-okta-sso-profile-setup.md | Use when an agent must install/verify AWS CLI v2, configure reusable SSO profile blocks, run Okta login, discover account/role, and confirm CLI auth without trial-and-error. | Data service lead | Draft |
| S3 Parquet → Snowflake stage, pipe, and load | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/s3-parquet-snowpipe-snowflake-cli.md | Use when an agent needs to generate and approve-first Snowflake landing SQL for Parquet files already in S3. | Data service lead | Draft |
| GitHub Actions Supabase backup to S3 | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/github-actions-supabase-to-s3-backup.md | Use when an agent needs to create a GitHub Actions workflow that performs a Supabase logical backup, archives it, uploads it to S3, and verifies syntax without running the job. | Data service lead | Draft |
| dbt PR data diff validation (Snowflake + BigQuery) | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/dbt-pr-data-diff-snowflake-bigquery.md | Use when an agent must generate or update PR-time data-diff scripts/workflow for changed dbt models and publish a markdown result as a PR comment/artifact. | Data service lead | Draft |
Streamlit in Snowflake - pilot access (ROLE_CHAT) | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/snowflake-streamlit-pilot-role-chat-access.md | Use when pilots cannot open SiS apps and explicit Streamlit USAGE grants must be discovered and applied. | Data service lead | Draft |
| dbt - Snowflake Cortex adoption marts + Analyst request logs | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/dbt-snowflake-cortex-adoption-analyst-logs.md | Use when a team needs repeatable local dbt setup plus a standard response to Analyst log authorization failures. | Data service lead | Draft |
| Data source memo (executive human style) | Data | Playbook | Per request | data-source-memo-executive-style-playbook.md | Use when an agent needs to create a one-page data source memo in plain executive language without technical formatting noise. | Data service lead | Draft |
| Data source discovery memo (new share / net-new tables) | Data | Playbook | Per engagement | data-source-discovery-memo-new-share-playbook.md | Use when profiling a new share or large net-new table set: confirm Snowflake vs BigQuery, auth, and schema access first; standard §1–§7-style structure, §3 table pattern, warehouse validation, executive tone, anti-fluff guardrails. | Data service lead | Draft |
| Data source discovery memo (additive update) | Data | Playbook | Per release | data-source-discovery-memo-update-playbook.md | Use when new tables land after a baseline memo: ask user for link or repo path to existing memo first; re-verify warehouse auth/scope; append §3.xx, update header dates, append-only executive summary and “what you’ll find,” do not rewrite frozen body without approval. | Data service lead | Draft |
| Edge-to-Activation Implementation | Data | Playbook | Per engagement | ../03-knowledge/edge-to-activation-implementation-playbook.md | Use when implementing Edge capture (CDN → warehouse → activation), phased testing, Cloudflare Worker reference architecture, or Linear/MCP setup for this offering. | Data service lead | Active |
| REST API → BigQuery ingest (curl, schema, target table) | Data | Playbook | Per engagement | ../delivery/service-lines/data/data-platform/playbooks/api-to-bigquery-ingest.md | Use when landing vendor REST JSON in BigQuery: user supplies complete curl, DDL + confirmed PK, then a Dagster job implements fetch, retries, pagination, CREATE TABLE IF NOT EXISTS, load, dedupe (Everflow-style; no ad-hoc BQ DDL/loads by implementer), 7-day / bounded windows. | Data service lead | Draft |
| OpenCode Desktop + Azure OpenAI (Brainforge) | Engineering | Playbook | Per engineer | ../03-knowledge/engineering/setup/opencode-desktop-azure-setup.md | Use when configuring OpenCode Desktop with Brainforge Azure OpenAI: East US (azure-eastus-gpt-* deployment providers or legacy azure-eastus, brainforge-openai, AZURE_KEY_BRAINFORGE_OPENAI / AZURE_OPENAI_EASTUS_API_KEY), MCP OAuth from CLI, repo root as workspace, and Desktop env for API keys. | Platform | Draft |
| KPI anomaly detection | Strategy & Analytics | Playbook | Per engagement | ../delivery/service-lines/strategy-analytics/measurement-kpis/playbooks/kpi-anomaly-detection.md | Use when a client or quarterly goal calls for recurring KPI anomaly detection with BigQuery-first ARIMA_PLUS, weekly retraining, hourly scoring, tuning to reduce false alerts, and rich notifications to Slack or email. | Strategy & Analytics service lead | Draft |
| Segment and Mixpanel Identity Resolution via Edge User ID | Data | Playbook | Per engagement | ../03-knowledge/segment-mixpanel-identity-resolution-playbook.md | Use when wiring Edge-to-Activation into Segment and Mixpanel with identity stitching: Edge ID propagation, Segment external ID resolution, Mixpanel destination configuration, and end-to-end validation. | Data service lead | Draft |
| GA4 vs Segment vs Mixpanel discrepancy investigation | Strategy & Analytics | Playbook | Per engagement | ../delivery/service-lines/strategy-analytics/measurement-kpis/playbooks/ga4-segment-mixpanel-comparison.md | Use when event, user, or conversion metrics diverge by >5% across GA4, Segment, and Mixpanel on a web property. | Strategy & Analytics service lead | Draft |
| Client Hour Overage Communications | Delivery Operations | Playbook | Per engagement | playbooks/client-hour-overage-communications-playbook.md | Use when client hours dedicated exceed billed hours — proactive outreach at 80%/90%/100% thresholds and reactive communication when overage occurs. Covers CSO/SL coordination, timeline, templates, and escalation. | Delivery Operations | Draft |