kaizen-wip

Identify in-progress work across Git worktrees, PRs, branches, and Kaizen cases.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-wip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen-wip
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-wip
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-wip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill surfaces in-progress work across git worktrees, open pull requests, unpushed branches, and active Kaizen cases to streamline triage and planning.

Core Features & Use Cases

  • Scan git worktrees and branches to surface in-progress work.
  • List open PRs and unpushed commits for quick visibility.
  • Track Kaizen cases linked to issues to coordinate follow-ups.

Quick Start

Ask Kaizen to scan your repository for in-progress work and return a concise report.

Frequently Asked Questions about kaizen-wip

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

FAQPage Schema
How do I find unpushed local branches and in-progress work across my git repository?

Finding unpushed local branches and in-progress work involves scanning git worktrees, open pull requests, and active Kaizen cases. This process returns a concise table-based summary with status metadata and cleanup recommendations for your repository.

What is the best way to track open pull requests and unpushed commits for triage?

Tracking open pull requests and unpushed commits for triage requires scanning your git worktrees and branches. This surfaces active work across your repository, returning a table-based summary with relevant metadata and practical follow-up task recommendations.

How does surfacing work-in-progress across git worktrees streamline repository planning?

Surfacing work-in-progress across git worktrees streamlines planning by consolidating unpushed branches, open pull requests, and active Kaizen cases. It provides a concise report with status and metadata to coordinate follow-ups and repository cleanup.

Can I list active Kaizen cases linked to issues for follow-up coordination?

Listing active Kaizen cases linked to issues is supported to coordinate follow-ups. The scan identifies these alongside open pull requests and unpushed branches, returning a concise table-based summary with metadata and cleanup recommendations.

Does this work-in-progress scan require external dependencies to run?

This work-in-progress scan requires no external dependencies. It applies directly across the current repository to list git worktrees, pull requests, branches, and Kaizen cases, returning a concise table-based summary with cleanup recommendations.