plan-executor:handover

You can ingest unstructured markdown plans by providing the file path to this Skill. It automatically detects the format, interactively collects missing execution metadata, and generates a meta.json sidecar file to prepare it for the execution pipeline.

Supported plan formats for automated pipeline ingestion include plan-executor markdown, Superpowers outlines, Claude Code outputs, and plain markdown or issue bodies. The Skill detects these formats to collect missing details and prepare deployment artifacts efficiently.

You collect missing execution metadata for a plan document by running this Skill in interactive mode. It prompts for essential details like goal, type, and target repository, or it fails deterministically in non-interactive mode to ensure pipeline integrity.

Yes, the plan-executor handover works with Superpowers outlines and Claude Code outputs. The format detection mechanism recognizes these specific structures alongside plain markdown, allowing you to integrate diverse plan documents into automated execution workflows.

In a non-interactive automated pipeline, plan ingestion fails deterministically if essential execution metadata is missing. This behavior prevents silent deployment failures by ensuring all required plan parameters are present before orchestrating dispatch to executors.

You prepare a meta.json sidecar for plan execution by pointing the Skill to your plan markdown file. It extracts or interactively gathers parameters like goal and target repository, writing them into the sidecar to orchestrate local or remote dispatching.