execution

Coordinate plan-driven task execution across parallel git worktrees.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill execution-nagasakah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/general-purpose/execution
Command: npx skills add https://github.com/NagasakaH/dev-process --skill execution-nagasakah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates end-to-end execution of development plans by orchestrating task delegation to sub-agents and managing parallel git worktrees, ensuring isolation and traceability.

Core Features & Use Cases

  • Plan-driven execution: delegates tasks to sub-agents and tracks progress across multiple branches.
  • Parallel worktree management: uses git worktree to run tasks in parallel while preserving repository integrity.
  • Execution history & integration: records progress, logs results, and supports cherry-pick-based integration into the main branch.

Quick Start

Provide an execution request to start running the plan using parallel worktrees.

Frequently Asked Questions about execution

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

FAQPage Schema
How do I automate task execution using parallel git worktrees?

Automating task execution with parallel git worktrees involves delegating plan-driven tasks to sub-agents and managing isolated workspaces to preserve repository integrity. This approach coordinates parallel branches and records execution history for structured integration.

What is plan-driven development execution and how does it work?

Plan-driven development execution delegates predefined tasks from a plan artifact to sub-agents and tracks progress across multiple branches. It applies worktree-based isolation to run tasks in parallel while monitoring and logging execution results.

Do I need a clean git repository to run parallel task execution?

Yes, running parallel task execution requires a pre-existing plan artifact like task-plan.md and a git repository with a clean state. The skill enforces worktree-based isolation to ensure repository integrity before delegating tasks to sub-agents.

How do I integrate parallel worktree commits into the main branch?

Integrating parallel worktree commits into the main branch relies on a structured cherry-pick process. The skill records execution history and logs results from isolated worktrees to support cherry-pick-based integration into the main branch.

Can I use sub-agents to manage task delegation across multiple branches?

Yes, you can use sub-agents to manage task delegation across multiple branches by orchestrating them through parallel git worktrees. This approach ensures isolated execution, tracks progress, and maintains traceability across the development plan.

What are the limitations of using git worktrees for parallel task management?

Limitations of using git worktrees for parallel task management include the strict requirement for a clean git repository state and a pre-existing plan artifact. Execution cannot proceed without these prerequisites, and integration relies entirely on structured cherry-picking.