guild-execute-plan

Dispatch per-lane tasks from an approved guild plan and collect handoff receipts.

6|Updated Apr 24, 2026

Search Tags:#workflow #backend #orchestration #handoff #guild #execute-plan

Ready to run

npx skills add https://github.com/lookatitude/guild --skill guild-execute-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guild-execute-plan
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/execute-plan
Command: npx skills add https://github.com/lookatitude/guild --skill guild-execute-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates execution of an approved guild plan by dispatching per-lane tasks and collecting handoff receipts, enabling end-to-end plan realization.

Core Features & Use Cases

Dispatch lanes according to the plan DAG, respecting depends-on relations and parallelism.
Gather per-lane context bundles and receipts into a run directory for downstream review.
Support both subagent and agent-team backends, with run-logging, assumption aggregation, and stop-condition checks.
Validate plan approval and per-lane artifacts before dispatch to prevent partial executions.

Quick Start

Run the execute-plan skill after a plan is approved to dispatch all lanes and collect handoff receipts.

Frequently Asked Questions about guild-execute-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate plan execution and dispatch tasks across parallel lanes?▼

Plan execution orchestration dispatches per-lane tasks according to the plan DAG, respecting depends-on relations and parallelism, then collects handoff receipts into a run directory for downstream review.

Can I execute a plan if the approval and per-lane context bundles are not staged?▼

No, executing a plan requires validated plan approval and staged per-specialist context bundles to prevent partial executions and ensure receipt integrity before dispatching any lanes.

What is the best way to coordinate backend selection for multi-lane plan dispatch?▼

Multi-lane plan dispatch supports both subagent and agent-team backends, handling backend selection, run-logging, and assumption aggregation automatically while enforcing per-lane context during execution.

How do I collect and review handoff receipts after dispatching a complex workflow?▼

Collecting handoff receipts happens automatically during plan execution by creating a run directory under .guild/runs, gathering per-lane context bundles, and producing a consolidated run state for downstream review.

Does plan execution support dependency management and stop-conditions for parallel tasks?▼

Yes, plan execution respects depends-on relations within the plan DAG for parallel task dispatch and includes stop-condition checks alongside run-logging and assumption aggregation during the orchestration process.