autopilot

Structured brainstorming for managed agents — one question at a time via ask_user, explores approaches before implementation.

Read a spec, execute every testable step, collect real results, then generate a podcast grounded in actual data — real API responses, real errors, real costs. Investigation first, narration second. Triggers: "investigate", "investigate this spec", "run and podcast", "investigate and podcast"

Produce a flight-podcast episode that steelmans a repo on engineering merits, then critiques it on file-pinned tensions. Local orchestration — research + dialogue happen under Claude Code supervision; render + Telegram delivery reuse the existing Pimsleur dispatch path. Invoked as `/autopilot podcast steelman OWNER/REPO`.

Use when turning any artifact (spec, plan, design doc, README, research notes) into a two-speaker podcast audio file. Triggers include "podcast", "make a podcast of", "turn this into a podcast", "podcast this spec".