blitz

Orchestrate parallel multi-issue sprints across isolated git worktrees with Claude agents.

5|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/Cygnusfear/claude-stuff --skill blitz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blitz
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/blitz
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill blitz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents. It orchestrates the full workflow from issue triage through parallel agent delegation to sequential merge, ensuring 100% issue coverage per agent.

Core Features & Use Cases

  • 100% Issue Coverage per Agent: Every agent MUST implement 100% of their assigned issue's requirements before their PR can be merged.
  • Worktree-per-issue Isolation: Creates independent git worktrees so agents operate in complete filesystem isolation.
  • Parallel Agent Execution: Spawns multiple Claude agents to work concurrently on separate issues.
  • PR Creation & Self-Review: Each agent creates a PR and self-reviews to 10/10 with full coverage.
  • Sequential Merge: PRs are merged one-by-one to avoid merge conflicts.

Quick Start

Create one worktree per issue and spawn parallel agents for multiple issues, ensuring each PR contains a 100% implementation of the issue requirements and closes the corresponding issue on merge.

Frequently Asked Questions about blitz

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

FAQPage Schema
How do I parallelize multiple GitHub issues across isolated git worktrees?▼

Parallelize multiple GitHub issues by creating one git worktree per issue and spawning independent Claude agents to work concurrently on each issue in complete filesystem isolation. Each agent implements 100% of their assigned issue's requirements, creates a PR with issue closure references, and self-reviews before sequential merge.

Can I run multiple Claude agents simultaneously on separate pull requests?▼

Yes, spawn parallel Claude agents to work on separate issues concurrently. Each agent operates in its own git worktree, ensuring isolation. After all agents complete their work and self-review to full coverage, PRs are merged sequentially to avoid conflicts.

What's the workflow for issue triage and parallel agent delegation?▼

Triage extracts all issues' requirements and ensures 100% coverage per agent. The skill guides agents through a 4-step loop: fix, review, iterate, and present. Each agent creates a PR including Closes references and a Related Issues section, then posts reviews via the GitHub API.

When should I use worktree-based parallelization instead of sequential issue fixes?▼

Use worktree parallelization when handling three or more independent GitHub issues in a sprint. Worktree isolation prevents merge conflicts and enables concurrent work, reducing total turnaround time compared to sequential fixes on a single branch.

Does this approach work for dependent issues or only independent ones?▼

This skill targets independent GitHub issues. Each agent works in complete filesystem isolation with 100% issue coverage per agent. Sequential merge orchestration prevents conflicts, but issues with cross-issue dependencies require manual coordination outside the parallel workflow.

How are merge conflicts prevented when multiple agents push PRs simultaneously?▼

Merge conflicts are prevented through sequential merge orchestration—PRs are merged one-by-one rather than concurrently. Each git worktree operates independently, and the skill coordinates the merge order to ensure clean integration without manual conflict resolution.