skills.rest
duanegoodner
duanegoodnerCOMMUNITY
Explore all skills by this author →
GitHub

parallel-assess

Analyze sprint PRs, dependencies, and target branches to produce parallelization plans with merge-order guidance.

Updated Feb 23, 2026
Search Tags:#worktree#parallel#code-review#pull-requests#development-workflow#merge-conflicts#pr-analysis
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill parallel-assess
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel-assess
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/parallel_assess
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill parallel-assess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assess whether remaining PRs in the current sprint can be worked on in parallel, each in its own git worktree.

Core Features & Use Cases

  • PR footprint analysis: Identify files touched by each PR and dependencies between PRs.
  • Conflict and merge risk assessment: Classify potential overlaps as independent, overlapping-safe, or conflicting.
  • Parallelization recommendations: Propose safe parallel groups and an optimal merge order.
  • Soft dependencies: Note improvements and potential sequencing considerations.
  • Use Case: Given a set of non-dependent PRs, determine which can run concurrently in separate worktrees.

Quick Start

Run the parallel-assess skill against the active sprint PRs to determine which can be worked on in parallel.

Frequently Asked Questions about parallel-assess

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

FAQPage Schema
How do I determine if pull requests can be worked on in parallel across git worktrees?▼

To determine if pull requests can be worked on in parallel across git worktrees, you analyze PR footprints, file overlaps, and dependencies to classify merge risks and output safe parallel groupings. This identifies independent PRs for concurrent execution.

What is the best way to identify merge conflicts and dependencies between pull requests in a sprint?▼

The best way to identify merge conflicts and dependencies between pull requests in a sprint is to analyze PR footprints to classify overlaps as independent, overlapping-safe, or conflicting. This assessment produces safe parallel groups and an optimal merge order.

How do I group non-dependent PRs for concurrent development without causing merge issues?▼

To group non-dependent PRs for concurrent development without causing merge issues, you evaluate PR file footprints and classify potential overlaps. This produces recommended parallelization plans with merge-order guidance, ensuring safe concurrent work in separate worktrees.

Does parallel PR analysis require specific git worktree configurations to assess sprint work?▼

Parallel PR analysis does not require specific git worktree configurations to assess sprint work. It evaluates PR footprints and dependencies directly to propose safe parallel groupings, allowing you to execute recommended non-dependent PRs concurrently in separate worktrees.

When should I not use parallel worktree groupings for pull request development?▼

You should not use parallel worktree groupings for pull request development when PR footprints are classified as conflicting rather than independent or overlapping-safe. The analysis identifies these merge risks, ensuring conflicting PRs are sequenced rather than grouped for parallel execution.

Can I get merge-order guidance for overlapping-safe pull requests?▼

Yes, you can get merge-order guidance for overlapping-safe pull requests. The analysis evaluates soft dependencies and potential sequencing considerations, outputting a recommended parallelization plan that includes an optimal merge order for safe execution.

Related Skills

Explore More Software Engineering Skills→
erclxerclx
2

git-followup

Stage, commit, and push follow-up edits to an open pull request branch.

Community
Advanced
aaronbassettaaronbassett
4

worktrees:orchestrator

Coordinate parallel development across subagents using isolated git worktrees.

Community
Intermediate
walid-moswalid-mos
2

swarm

Orchestrate specialized AI agents to complete software development tasks via Git.

Community
Advanced
edmundmilleredmundmiller
78

Understanding Jujutsu Merges and Conflicts

Explain Jujutsu merge semantics, empty merge commits, and conflict resolution.

Community
Advanced