Decompose large specs into sequenced PRs with dependency graphs and sub-issues.
npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-plan
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
Decomposes large initiatives into independent, sequenced PRs with one issue per PR, enabling controlled scope, predictable delivery, and traceability.
Decompose the current kaizen-prd spec into independent PRs and create a dependency graph with per-PR issues.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
naopensedoit2-designGenerate PRDs, user stories, acceptance criteria, and roadmaps from product ideas.
allenhutchisonAutomate nightly TypeScript architecture audits that route discrete findings to PRs or issues.
CERTCCCreate GitHub Epics with standardized issue types and labels.
hatch3rRegenerate the living project board overview from scanned work items.
