kaizen-plan

Name: kaizen-plan
Availability: InStock
Author: Garsson

Decompose large specs into sequenced PRs with dependency graphs and sub-issues.

Updated Mar 16, 2026

Search Tags:#workflow #planning #pr #kaizen #issue-management #dependency-graph

Ready to run

npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kaizen-plan
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-plan
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes large initiatives into independent, sequenced PRs with one issue per PR, enabling controlled scope, predictable delivery, and traceability.

Core Features & Use Cases

Decompose a spec into discrete PRs with clear ownership and acceptance criteria.
Generate a dependency graph and phased plan to guide work and risk assessment.
Create thin sub-issues linked to the epic to track implementation work without content drift.

Quick Start

Decompose the current kaizen-prd spec into independent PRs and create a dependency graph with per-PR issues.

Frequently Asked Questions about kaizen-plan

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

FAQPage Schema

How do I decompose a large spec into independent pull requests?▼

Decomposing a large spec into independent pull requests involves breaking the epic into discrete, sequenced PRs with one issue per PR to ensure controlled scope. This generates a dependency graph and phased plan for risk assessment.

What is the one issue per PR workflow for issue management?▼

The one issue per PR workflow links thin sub-issues directly to an epic, ensuring traceability and preventing content drift during development. Each independent pull request receives clear ownership and acceptance criteria for predictable delivery.

Can I generate a dependency graph and phased plan from an existing spec?▼

Yes, you can generate a dependency graph and phased plan from an existing spec document. The system analyzes the large initiative to guide work sequencing, assess risks, and produce sub-issues ready for development linked to the original epic.

Do I need a spec document to create a phased plan and sub-issues?▼

Yes, you need a spec document produced by a product requirements process to create a phased plan and sub-issues. The planning phase requires this existing specification to decompose the work into independent pull requests with accurate dependency mapping.

Why create sub-issues linked to the epic for pull request planning?▼

Creating sub-issues linked to the epic tracks implementation work without content drift across multiple pull requests. This maintains traceability between the original spec and the sequenced PRs, ensuring controlled scope and clear ownership throughout delivery.

What are the limitations of planning pull requests with a single issue per PR?▼

Planning pull requests with a single issue per PR requires a completed spec document as input. Without this prerequisite specification, the workflow cannot generate the dependency table, phased plan, or linked sub-issues needed for accurate risk assessment and sequencing.