Tools and workflows: overview¶
The stack you use as an FA. Tool names are locked; the workflows are still being built — see the confirmed gap below.
GitHub is the source of truth. Most of what these tools surface ultimately lives in a repo in the scailetech org — the GitHub map says which repo holds what, and you can query any of them in Claude Code.
| Tool | Purpose | Your touch |
|---|---|---|
| Claude Code | Primary execution surface for FA work | Heavy use, daily — claude-code-and-mcp.md |
| MCPs | Connect Notion, Gmail, Drive, Slack, Granola to Claude | Configure once, use constantly — claude-code-and-mcp.md |
| Granola | Primary meeting transcription | On for every meeting — granola-to-doc-pipeline.md |
| Fireflies | Secondary meeting capture | Reference only |
| Notion | Venture builds, knowledge base | Write & maintain |
GitHub (scailetech org) |
Code, client DB, ventures | Read; write only on assigned repos — github-map.md |
| Linear | Engineering tasks | Read for context; never write without direction — linear-and-tasks.md |
| Twenty CRM | Client + contact database | You maintain it — crm-and-twenty.md |
| Vercel | Front-end deploys for ventures and client sites | Deploy on assigned ventures; never production without sign-off — vercel-render-supabase.md |
| Render | Back-end / API hosting | Engineering only by default — vercel-render-supabase.md |
| Supabase | Database, auth, storage for ventures | Under scailetech only — vercel-render-supabase.md |
| Bitwarden | Password manager | Day-one provisioning |
| Slack | Internal comms | Daily — ../06-where-things-live/slack-map.md |
Confirmed gap¶
There is no standard SCAILE workflow for Claude Code + MCP usage. Everyone improvises. Building the shared library of skills, prompts, and motions is itself an early FA contribution — see claude-code-and-mcp.md.
Owner: Current FA Last reviewed: 2026-07-03