run-plan

Execute the next phase of a plan document with verification and reporting.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill run-plan-zillabunny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-plan
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/run-plan
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill run-plan-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-driven development often suffers from misaligned phases, manual handoffs, and unclear progress tracking. This Skill automates the orchestration of plan phases, ensuring deterministic progression, traceable commits, and consistent reporting across the lifecycle.

Core Features & Use Cases

  • Phase progression: parse plan, identify the next incomplete phase, dispatch implementation, and update progress.
  • Dual execution modes: worktree-based implementation or delegate-on-main execution.
  • Verification, progress tracking, and reporting: write plan reports (plan-{slug}.md) and optionally auto-land to main; support cron-based scheduling for autonomous runs.
  • Safety checks: dependency validation, staleness detection, and clear failure handling.

Quick Start

Provide the plan file path to run and let the orchestrator execute the next phase while updating progress.

Frequently Asked Questions about run-plan

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

FAQPage Schema
How do I automate plan-driven development phase progression?

Automate plan-driven development by parsing a plan document, identifying the next incomplete phase, and dispatching implementation. The orchestrator executes phases sequentially and generates traceable reports to ensure deterministic progression across the lifecycle.

What is the best way to track progress and report on a development plan?

Track development plan progress by generating plan reports (plan-{slug}.md) and updating the plan document after each phase. This approach ensures traceable commits and consistent reporting, replacing manual handoffs with automated progress tracking.

Can I execute plan phases in a worktree or delegate directly on main?

Yes, you can execute plan phases using either worktree-based implementation or delegate-on-main execution. Dual execution modes support isolated development via worktrees or direct execution on the main branch depending on your workflow needs.

How do I schedule autonomous plan orchestration runs with cron?

Schedule autonomous plan orchestration runs using cron-based scheduling to automatically execute the next phase. This optionally auto-lands verified changes to main, coordinating verification and progress tracking without manual intervention.

Does plan orchestration enforce dependency safety and handle failures?

Yes, plan orchestration enforces dependency safety through validation and staleness detection before execution. It provides clear failure handling and verification checks to ensure only validated phases progress, preventing misaligned or unsafe commits.

Do I need a specific plan file format to start plan automation?

You need to provide a plan file path containing structured phases to start plan automation. The orchestrator parses this document to identify incomplete phases, dispatch implementation, and update progress, requiring no additional dependencies.