RecapFlow : June 16th Coaching call analysis
π SUMMARY This week's call opened with the community offering condolences to Patrick Chouinard and Paul Miller, who both recently experienced family losses. Patrick shared how Claude helped him compress two months of estate administration into 48 hours during his bereavement. The technical discussion centered on coping strategies following the sudden unavailability of Anthropic's Fable model, with members sharing alternative workflows combining Claude Opus 4.8, Codex GPT-5.5, and the emerging Fusion architecture. A strong consensus emerged around the danger of automating broken business processes, alongside practical demonstrations of adversarial prompting and agent scaffolding strategies. π‘ KEY INSIGHTS Estate administration acceleration: Claude processed funeral home paperwork and proactively searched government websites for required forms and benefits, reducing administrative burden from months to hours while demonstrating unexpected emotional sensitivity by pacing tasks and flagging only time-sensitive items. Deterministic over autonomous: Keep systems as deterministic as possible, using AI decision-making only where necessary. The value in coming years lies in scaffolding and infrastructure rather than end-to-end autonomy. Model specialization: For terminal, infrastructure, and script work, GPT-5.5 (Codex) currently outperforms Claude Opus 4.8, while Opus remains superior for UI-backed application development. Adversarial prompting: Patrick's system prompt configures Claude as a challenging business analyst that asks "what problem are you actually trying to solve?" rather than accepting stated solutions at face value. Placed in Claude.md at the user level, it applies to every session including Claude Code. Process integrity warning: AI amplifies broken business processes rather than fixing them, making dysfunction bigger and more visible. Intention is a muscle that atrophies when over-relying on highly autonomous models. Intent queue workflow: Ty's method uses Claude's background commands to capture context-rich questions, storing them locally to surface as a primed queue at the next session, saving token spend on re-priming.