pll

Launch multiple blueprints in parallel across isolated git worktrees.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill pll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pll
Source: https://github.com/ozby/node-pubsub/tree/main/.agent/skills/pll
Command: npx skills add https://github.com/ozby/node-pubsub --skill pll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and safely executing multiple blueprint plans in parallel without crossing their workspaces.

Core Features & Use Cases

  • Independently run multiple blueprints by creating isolated git worktrees for each lane.
  • Guarantees that commits are made only after verification gates pass, preventing partial merges.
  • Use case: accelerate delivery by running multiple blueprints concurrently while preserving per-lane isolation.

Quick Start

Invoke with the pll command and a list of slugs to launch parallel lanes.

Frequently Asked Questions about pll

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

FAQPage Schema
How do I run multiple blueprint plans in parallel without crossing workspaces?

Running blueprints in parallel across isolated git worktrees keeps each workspace separate. This approach creates per-lane isolation so concurrent execution never crosses boundaries, accelerating delivery safely.

What is the best way to prevent partial merges during parallel orchestration?

Preventing partial merges during parallel orchestration requires strict commit gating. Commits occur only after verification gates pass, ensuring no unverified or incomplete work gets merged into the isolated lanes.

How does git worktree orchestration work for phase-based execution?

Git worktree orchestration for phase-based execution creates isolated worktrees per slug. Each lane runs independently through its phases, preserving strict per-lane isolation while executing concurrently.

Can I use isolated git worktrees to coordinate concurrent delivery lanes?

Isolated git worktrees coordinate concurrent delivery lanes by mapping each slug to its own workspace. This preserves per-lane isolation and ensures commits happen only after verification gates pass.

Do I need verification gates to commit parallel worktree changes?

Verification gates are required before committing parallel worktree changes. Strict commit gating ensures commits occur only after verification passes, preventing partial merges and maintaining per-lane isolation.

When should I not use parallel worktree orchestration for blueprints?

Parallel worktree orchestration should be avoided when blueprints require shared workspace state or lack independent execution paths. It suits concurrent delivery needing per-lane isolation and strict commit gating.