AI Agents: Automation

Personal Automation with Subagents

• Claude Code subagents running in parallel with scoped tool access is the key capability enabling complex personal automation -- six independent workers holding different contexts simultaneously (from jimprosser chief of staff claude)
• Never let AI send emails autonomously (only draft), never make pricing decisions, default to "prep" (80% ready) rather than "dispatch" (fully handled) when uncertain (from jimprosser chief of staff claude)
• Layered automation compounds: overnight inbox scan improves morning triage, better triage enables subagent dispatch, reliable dispatch makes time-blocking viable -- 36 hours of work compounds on itself (from jimprosser chief of staff claude)

Agent-First Operations

• Marcus Moretti runs Spiral at Every as a one-person team (PM + code + support + marketing) — replaced 60% of a PM's old week with two files and a cron job: strategy.md (target problem, audience, 3-5 SMART metrics, 2-4 work tracks) and /ce:product-pulse running at 8am reading PostHog/Stripe/Datadog/database into ~/pulse-reports/ (from ai agent pm workflow spiral every)
• Now/Next/Later kanban with In Progress/Done — no sprints, no standups, no PRDs, no backlog grooming, no stakeholder updates; the agent writes tickets, moves them, and keeps statuses live (from ai agent pm workflow spiral every)
• The MCP-as-survival rule: vendors without MCPs become unusable in agent-driven workflows ("didn't have an MCP, and it was swiftly cancelled") — average company runs ~100 SaaS subscriptions and a meaningful slice now has a 12-month death timer (from ai agent pm workflow spiral every)
• New role definition: whatever the agent can't read, the PM can't use; whatever the PM can't use becomes someone else's job — the JD follows the agent's affordances (from ai agent pm workflow spiral every)
• "Agent engineer" is emerging as an internal-FDE role — extremely technical, embedded with business teams, wires up secure governed agents to Box/Salesforce/Workday and codifies workflows in skills; "agent product management" is the matching business-side role (from agent engineering roles internal business processes)
• The shift is from automating jobs to automating processes — agent engineers span teams/functions because the unit of automation is now the cross-functional process, not the role (from agent engineering roles internal business processes)
• OpenAI's "Lord Bottleneck" pattern: a growth-team staffer used Codex for individual experiment steps (analyze data, write experiment code, interpret results, produce deck), then chained them into one giant skill, then asked "do this every morning" — a self-bootstrapped cron-driven experiment loop with significant company value (from openai lord bottleneck codex automation)
• Build incrementally and personify: start with single-task acceleration (don't try to automate the whole pipeline), connect successful pieces into a skill, then schedule it; naming the system ("Lord Bottleneck") makes it approachable for the team (from openai lord bottleneck codex automation)
• Browserbase's open-source skills catalog turns web-agent automation into a playbook distribution problem: researched site behaviors become reusable capabilities instead of bespoke automation code for every target (from browserbase web agent skills catalog)
• claude-smart can reduce planning iterations and token usage by 70%+ on similar future tasks by storing reusable local learnings from previous sessions, making self-improvement an automation primitive rather than a memory side effect (from claude smart self improving plugin)
• Every automated everything it could with AI agents but still grew from 4 to 30 human employees since GPT-3, suggesting agent automation can increase the volume of valuable human coordination, oversight, and strategic work (from ai automation increases human work demand)
• Coding-agent best practices at scale can invert within six months, so agent automation programs need regular reassessment loops instead of assuming an operating style remains optimal (from coding agents large scale projects learnings)

Personal Agent Requirements

• Peter Yang's framework for an ideal personal agent: works across email/calendar/Workspace/any MCP, acts proactively (cron, triggers, follow-ups), has memory that "just gets you" over time, works on web and mobile without slash commands, switches text/voice/video/live calling mid-conversation, is reachable from any messenger, and has personality that's fun to talk to (from personal agent requirements framework)
• None of OpenClaw, Claude Code, or Codex check all seven personal-agent boxes yet — the bar for "personal" agents is significantly higher than the bar for engineering agents (from personal agent requirements framework)