plan-execute

Execute validated plans in isolated git worktrees and merge results via pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end execution of validated plans within isolated worktrees, enabling automated verification, task-level execution, and seamless merge via PR.

Core Features & Use Cases

  • Isolated worktree execution: runs plans in dedicated git worktrees to avoid side effects.
  • TDD scaffolding: sets up tests for planned tasks and tracks failures before implementation.
  • Level-based parallel execution: runs multiple tasks concurrently per layer with per-task agents.
  • Quality gate and smoke testing: enforces validation and pre-merge checks.
  • PR creation and automated merge: opens and merges a PR when plan tasks complete.

Quick Start

Provide a validated plan at .worktrees/<feature-name>/plans/YYYY-MM-DD-<feature-name>.md and run the plan-execute skill to execute it through to a merged PR.

Frequently Asked Questions about plan-execute

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

FAQPage Schema
How do I automate pull request creation from a validated development plan?

You can automate pull request creation by running validated plans through this Skill, which executes tasks in isolated git worktrees, enforces quality gates, and automatically opens and merges a PR upon completion.

How does test-driven development scaffolding work with isolated git worktrees?

TDD scaffolding with isolated git worktrees works by setting up tests for planned tasks and tracking failures before implementation, ensuring side-effect-free execution within dedicated worktree branches.

Can I run multiple plan tasks concurrently using per-task agents?

Yes, you can run multiple plan tasks concurrently through layer-based parallel execution, which assigns per-task agents to execute tasks within the same layer simultaneously for faster completion.

Do I need a specific plan file format to execute development plans automatically?

Yes, you need a validated plan file format located at .worktrees/<feature-name>/plans/YYYY-MM-DD-<feature-name>.md to execute development plans automatically through the automated PR workflow.

What's the best way to enforce quality gates before merging automated pull requests?

The best way to enforce quality gates before merging automated pull requests is by using built-in validation and smoke testing features that run pre-merge checks during the plan execution phase.

Why use isolated git worktrees for automated plan execution?

Isolated git worktrees are used for automated plan execution to avoid side effects, allowing per-task agents to run tests and implementations in dedicated branches without affecting the main repository state.