What is a parallel workflow retrospective?

It is a systematic review of how multiple parallel tasks were executed, using git data to identify lessons learned and improve future coordination.

Which branches does the retrospective analyze?

It typically examines worker branches (work/task-*), integration branches, and compares them against the main development branch.

What are the key metrics evaluated during a review?

It evaluates commit frequency, time spent in 'blocked' states, complexity estimation accuracy, and the frequency of merge conflicts.

Does this skill modify my code or git history?

No, the skill operates in a strictly read-only mode. It analyzes branches and commits to generate reports but never creates or modifies them.

Can it identify why a parallel task failed?

Yes, by analyzing [BLOCKED] and [NEEDS] tags in commit messages, it can pinpoint dependencies or technical hurdles that caused a workflow to stall.

Parallel Workflow Retrospective

Name: Parallel Workflow Retrospective
Author: jimmc414

byjimmc414

•

生産性とワークフロー

Analyzes completed parallel git workflows to identify bottlenecks, evaluate planning accuracy, and provide actionable process improvements.

Parallel Workflow Retrospective is a specialized analysis tool designed to evaluate the execution and efficiency of multi-worker parallel tasks. By examining git history, commit patterns, and branch distributions, it reconstructs the timeline of complex workflows to pinpoint where delays occurred, why workers were blocked, and how accurately the initial work was estimated. It provides a data-driven post-mortem that helps users refine their parallelization strategies, improve commit discipline, and optimize future project orchestration—all while operating in a strictly read-only mode to ensure repository integrity.

主な機能

01Automated git history reconstruction and chronological timeline analysis

021 GitHub stars

03Verification of convention adherence for commit prefixes and branch naming

04Root cause analysis for blocked tasks and unresolved cross-dependencies

05Quantitative assessment of planning complexity versus actual execution time

06Detection of work distribution imbalances and cross-worker scope violations

ユースケース

01Diagnosing the root causes of workflow failures or significant merge conflicts

02Auditing team or AI agent adherence to standardized git workflow conventions

03Conducting detailed post-mortem reviews after complex parallel feature implementations

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jimmc414/claude-code-plugin-marketplace parallel-retrospective

For use in Claude.ai and ChatGPT

Download Skill