worktree-kickoff

Coordinate PR development in an existing worktree with parallel PR awareness.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-kickoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-kickoff
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/worktree_kickoff
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-kickoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kick off development for a single PR inside the current worktree, with awareness of other PRs being worked on concurrently. This skill assumes the worktree already exists (created via /worktree_setup) and that Claude Code was launched with this worktree as its workspace root.

Core Features & Use Cases

  • Parallel-awareness for kickoffs inside a shared worktree.
  • Reads current branch, active sprint doc, and PR specs to align changes.
  • Helps surface a mid-level plan while avoiding conflicts.

Quick Start

Provide the target PR identifier and optional parallel-with PRs, then run the kickoff to align and prepare the current worktree for parallel development.

Frequently Asked Questions about worktree-kickoff

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

FAQPage Schema
How do I coordinate parallel PR development within a single git worktree?

To coordinate parallel PR development within a git worktree, you provide a target PR and optional parallel-with PRs. The kickoff process reads the current branch, active sprint doc, and surrounding PR specs to align changes and surface a mid-level plan.

What do I need to set up before kicking off PR work in an existing worktree?

Before kicking off PR work in an existing worktree, you need the worktree already created and set as the workspace root. You also need an active sprint doc and available PR specs to align the concurrent branch changes.

How does worktree parallel-awareness prevent branch conflicts during sprint development?

Worktree parallel-awareness prevents branch conflicts by reading surrounding PR specs and recent commits during the kickoff. This mid-level planning approach aligns concurrent changes across multiple PRs within the same sprint.

Can I use a sprint doc to align multiple concurrent PRs in the same worktree?

Yes, you can use an active sprint doc to align multiple concurrent PRs in the same worktree. The kickoff process explicitly reads the sprint doc alongside the current branch and PR specs to coordinate parallel development.

When should I avoid using a parallel-aware worktree kickoff for branch coordination?

You should avoid using a parallel-aware worktree kickoff if the worktree does not already exist or was not set as the workspace root. It also provides limited value if you lack active sprint docs or surrounding PR specs to align changes.