kiln-distill

Bundle open issues, feedback, and roadmap items into feature PRDs.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-distill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiln-distill
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/kiln-distill
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill kiln-distill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Kiln Distill skill bundles open backlog items from .kiln/issues/, reads strategic feedback from .kiln/feedback/, and gathers structured roadmap items from .kiln/roadmap/items/ to generate a cohesive feature PRD. It orchestrates multiple input streams, applies phase/addresses/kind filters, and preserves a deterministic frontmatter order to support downstream automation.

Core Features & Use Cases

  • Consolidates three input streams into a single narrative PRD.
  • Groups items by themes (feedback-led, item-led, and issue-only) with deterministic sorting.
  • Supports --phase, --addresses, and --kind filters to scope roadmap items; gracefully handles empty inputs.

Quick Start

Invoke /kiln:kiln-distill with your desired filters to generate a per-theme PRD from open feedback, roadmap items, and issues.

Frequently Asked Questions about kiln-distill

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

FAQPage Schema
How do I turn open backlog issues and feedback into a feature PRD?

To generate a feature PRD, bundle open backlog items from .kiln/issues/, strategic feedback from .kiln/feedback/, and structured roadmap items from .kiln/roadmap/items/ into a single cohesive narrative document grouped by selected themes.

Can I filter roadmap items by phase or kind when generating a PRD?

Yes, you can scope roadmap items during PRD generation by applying --phase, --addresses, and --kind filters. This selects specific roadmap entries and shapes the narrative output accordingly.

How does distilling a PRD from multiple input streams handle deterministic output?

Deterministic PRD output is ensured by grouping items into feedback-led, item-led, and issue-only themes with fixed sorting, and emitting frontmatter with a strict three-group derived_from ordering: feedback, then items, then issues.

What happens if .kiln/feedback/ or .kiln/issues/ directories are empty when bundling a PRD?

When generating a PRD with empty input directories, the process gracefully handles the missing data and continues bundling the available roadmap items and issues without failing the operation.

What is the best way to consolidate roadmap items and customer feedback into product requirements?

The best way to consolidate these streams is to group them by themes using phase and kind filters, producing one structured PRD per selected theme with deterministic frontmatter for downstream automation.

Do I need structured roadmap items before generating a feature PRD?

You need structured roadmap items from .kiln/roadmap/items/ to shape the PRD narrative, but the process gracefully handles empty feedback or issues directories if those streams are currently blank.