execute-plan

Name: execute-plan
Availability: InStock
Author: VirtEngine

Execute PLAN.md by spawning subagents and generating SUMMARY.md with outcomes.

17|4|Updated Oct 8, 2021

Search Tags:#automation #orchestration #checkpoints #git-commit #deviations #execute-plan

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the execution of phase plans by coordinating autonomous subagents with a central orchestration context, delivering a complete SUMMARY.md and an auditable execution history.

Core Features & Use Cases

Orchestrates multi-segment phase plans using subagents and a main context
Manages checkpoints, human-in-the-loop actions, and authentication gates
Generates SUMMARY.md with aggregated results and a detailed task history for audits

Quick Start

Initiate the execute-plan workflow against the active PLAN.md to produce a SUMMARY.md and a full execution log.

Frequently Asked Questions about execute-plan

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

FAQPage Schema

How do I orchestrate phase plans using subagents for autonomous execution?▼

Plan orchestration coordinates multi-segment execution by reading PLAN.md, spawning subagents for autonomous segments, and generating a SUMMARY.md with aggregated outcomes and a detailed task history.

How do I manage checkpoints and authentication gates during plan execution?▼

Plan execution manages checkpoints and authentication gates by applying central orchestration context, recording deviations, and handling human-in-the-loop actions to ensure autonomous segments respect planning configurations.

Can I automate git commits when executing a multi-phase development plan?▼

Yes, plan execution loads project context and commits results according to the guidelines defined in your PLAN.md, ensuring automated git commits align with the configured phase requirements.

How do I generate an auditable execution history and summary for a multi-segment plan?▼

Executing a phase plan generates a SUMMARY.md containing aggregated results and a detailed task history, providing an auditable execution log that records deviations and outcomes from all subagents.

Does plan orchestration work without external dependencies or components?▼

Yes, the orchestration workflow operates without external dependencies or components, relying solely on reading PLAN.md and managing subagents to produce the final SUMMARY.md output.

What is the best way to handle deviations when running autonomous phase plans?▼

Plan orchestration handles deviations by recording them during subagent execution and aggregating these exceptions into the final SUMMARY.md, ensuring all anomalies are auditable alongside successful outcomes.