kta-prd-pipeline

Generate per-feature PRDs with nested screens from validated idea briefs.

4|Updated May 7, 2026
One-click install
npx skills add https://github.com/dantech0xff/dreams --skill kta-prd-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kta-prd-pipeline
Source: https://github.com/dantech0xff/dreams/tree/main/.agents/skills/kta-prd-pipeline
Command: npx skills add https://github.com/dantech0xff/dreams --skill kta-prd-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decompose validated idea briefs into structured, per-feature PRDs with nested screens, ensuring consistent design specifications and scalable planning.

Core Features & Use Cases

  • Phase-driven PRD generation: decompose idea briefs, create per-feature PRDs, and build cross-feature navigation artifacts.
  • Enforce governance: fixed 5 journey buckets and a hard cap of 8 features to keep MVP scope manageable.
  • Outputs include INDEX.md, nav-graph.mmd, and plans/{slug}/prd/{NN}-{feature-slug}.md to feed downstream design tools.

Quick Start

Run the kta-prd-pipeline after you place plans/{slug}/idea-brief.md to generate the PRD directory and navigation artifacts.

Frequently Asked Questions about kta-prd-pipeline

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

FAQPage Schema
How do I generate per-feature PRDs from a validated idea brief?

To generate per-feature PRDs, place plans/{slug}/idea-brief.md and run the pipeline to decompose validated feature seeds into structured Markdown files, INDEX.md, and nav-graph.mmd.

What is the maximum number of features allowed in a feature PRD pipeline?

The feature PRD pipeline enforces a hard cap of max 8 features and fixed 5 journey buckets to keep MVP scope manageable and ensure consistent design specifications.

How do I create a cross-feature navigation graph for my design specs?

Cross-feature navigation is generated automatically by reading your idea brief and emitting a nav-graph.mmd file alongside per-feature PRD Markdown files to feed downstream design tools.

Do I need a specific idea brief format before generating feature PRDs?

Yes, the pipeline requires plans/{slug}/idea-brief.md with validated feature_seeds to operate and decompose ideas into per-feature PRDs with nested screens.

Can I include monetization features when decomposing an idea into PRDs?

No, the pipeline enforces a non-monetization focus and outputs only Markdown PRD files, strictly avoiding monetization features to maintain standardized MVP scope.

Why is my feature PRD pipeline not generating the expected INDEX.md file?

The pipeline fails to generate INDEX.md if plans/{slug}/idea-brief.md is missing or feature_seeds validation fails, requiring correct upstream idea brief placement first.