Treating Claude like a new teammate: one Slack message, QA bug report in 96 minutes
max_gladysh · reddit · 2026-09-11
BotsCrew's team kept hitting the same problem: every engineer had their own AI setup — prompts, context, tricks — and all of it evaporated when that person left or went on leave, forcing meetings and Slack archaeology to reconstruct context.
Their fix wasn't a better prompt but treating Claude like a new teammate with three things:
- Instructions: stable info — role, project goals, who's who, tools in play.
- Context: live data pulled via connectors (Slack, ticketing, call recordings) instead of copy-paste.
- Playbooks: SOPs extracted from chats that already worked.
The proof: a dev documented his research in a shared Claude project while working on a gnarly integration, then handed off with a single Slack link before going on leave — no meeting, no doc dump. QA picked it up with full context and returned a detailed bug report 96 minutes later.
They now run four parallel agents for weekly client report prep, checking call recordings and integration status to draft updates automatically. No day-to-day workflow changes required — just moving AI setup from personal config to shared project resource.
More from coding & agent
- Astra builds a surprisingly polished Catan game in three.js, reusing past UI and 3D assets — FinanceYF5 · 2026-09-11
- Open-Source Tool Highlights the Exact PDF Paragraphs Behind AI Answers — Flat-Phone-1596 · 2026-09-11
- OpenAI Codex may issue another usage reset this weekend, says Codex lead resets happen — umesh_ai · 2026-09-11
- Dev swaps gemini-3.8 for gemini-3.5-flash-lite in his MCP harness at a fraction of cost — julianharris · 2026-09-11
- ComfyUI Style Explorer Adds LoRA Preview Catalog and Sharing — neonsparksuk · 2026-09-11
- User burns $200 of Codex credits in one agent turn — 4,700 of 5,000 credits, task unfinished — RileyRalmuto · 2026-09-11