← ClaudeAtlas

octoplan-autopilotlisted

Use when the user says "Octoplan Autopilot" followed by a work-stream name, when the user asks for a work stream to be planned and then delivered under supervision or autonomously, when an Octopad work stream needs turning into an execution-ready plan, when a task marked "Octoplan flesh-out required" needs speccing, or when a session executing a planned stream discovers something that adds a task or changes the order — it invokes this skill to rebalance the plan. Planning is implementation-free until the user's explicit delivery go; after that go the stream is supervised, by that same session or by a fresh supervisor session it hands to. When installed it supersedes the planning-only Octoplan skill, so use it for a plain "Octoplan" request too. Requires a connected Octopad MCP server.
sudolab-co/octopad-mcp · ★ 0 · AI & Automation · score 67
Install: claude install-skill sudolab-co/octopad-mcp
Version: 0.2.0 # Octoplan Autopilot — work-stream planning and supervised delivery for Octopad Octoplan Autopilot turns an Octopad work stream into a plan of detailed, ordered, self-contained tasks, and then — once the user says go — supervises their delivery, either from the planning session or from a fresh supervisor session it hands to. It works for any kind of stream — engineering, marketing, content, operations, legal — because Octopad holds the plan, the state, and the order: any session working the stream briefs itself from Octopad and needs nothing else. **Everything a later session needs lives in the task itself.** A session that picks a task up has no memory of this one and normally does not load this skill, so the planner writes its hand-off instruction into the task description, verbatim, using the patterns below. That holds for the supervised path too: it is what lets a fresh session take the stream over if this one dies. The one exception is replanning (see Replanning): a session whose discovery changes the plan loads this skill to rebalance it. ## Resuming a stream — check this first Before planning anything, look at the stream you were invoked on. If ALL THREE hold — its name already ends with ` (octoplanned)`, it carries the delivery contract's Decisions, and one of those Decisions records a delivery go the user has not withdrawn — then this is a resume, not a new plan. Do not re-plan, do not re-run the brief, do not re-ask for the dials, and do not re-a