kaizen-prd

Formalize problem space, solution scope, and governance into a durable PRD.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planable, durable PRDs are needed to capture complex initiatives before implementation, ensuring context survives issue closures and handoffs.

Core Features & Use Cases

  • Structured problem space to capture root cause, evidence, and constraints.
  • Iterative discovery workflow guiding stakeholders to a stable spec.
  • Output artifacts: a docs PRD and a GitHub epic issue with references for implementation.

Quick Start

Describe the initiative and generate a complete PRD draft that can be saved to docs/prd-kaizen-prd.md.

Frequently Asked Questions about kaizen-prd

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

FAQPage Schema
How do I write a durable PRD that captures problem space and solution scope?

To write a durable PRD, formalize the problem space, solution scope, and governance by guiding iterative discovery. This captures root cause, evidence, and constraints to ensure context survives issue closures and team handoffs.

What is the best way to structure a product specification for complex initiatives?

The best way to structure a product specification is to enforce a structured spec containing a problem statement, end state, roles, architecture, interaction models, state management, risks, and open questions.

How do I generate a GitHub epic issue from a product requirements document?

You can generate a GitHub epic issue from a PRD by formalizing the document into a tracking anchor. This produces an epic issue with references for implementation alongside an optional docs PRD file.

Does this PRD planning workflow support iterative discovery with stakeholders?

Yes, this PRD planning workflow supports iterative discovery by guiding stakeholders to a stable spec. It documents decisions throughout the process to ensure a durable, issue-proof product requirements document.

When do I need a formal PRD with governance documentation?

You need a formal PRD with governance documentation when planning complex initiatives before implementation. It ensures that existing versus needs-building components, risks, and open questions are documented for long-term durability.

Can I save the generated PRD draft directly to my docs folder?

Yes, you can save the generated PRD draft directly to your repository. The workflow produces an optional docs PRD file that can be saved to docs/prd-kaizen-prd.md for future reference.