bmad-distillator

Compress source documents into lossless token-efficient distillates for LLM consumption.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/LinCie/bearuang --skill bmad-distillator-lincie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-distillator
Source: https://github.com/LinCie/bearuang/tree/main/.opencode/skills/bmad-distillator
Command: npx skills add https://github.com/LinCie/bearuang --skill bmad-distillator-lincie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Feeding large sets of source documents (briefs, discovery notes, research reports) into downstream LLM workflows wastes tokens on prose, transitions, and repetition, while naive summarization loses critical facts, decisions, and constraints. ## Core Features & Use Cases - Lossless Compression: Extracts every fact, decision, constraint, and relationship from source documents into dense, thematically-grouped bullet distillates with YAML frontmatter. - Semantic Splitting: Automatically splits large distillates into self-contained section files with an index when content exceeds token thresholds or a user-specified token budget. - Round-Trip Validation: Optionally reconstructs original documents from the distillate alone and produces a validation report flagging gaps and hallucinations. - Use Case: Before writing a PRD, distill a product brief plus its discovery notes into a single ~1,500-token distillate that a downstream planning agent consumes as sole context without information loss. ## Quick Start Distill the documents product-brief.md and discovery-notes.md into a distillate for PRD creation, then run it with the --validate flag to confirm nothing was lost.

Frequently Asked Questions about bmad-distillator

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

FAQPage Schema
How do I compress documents for LLM context without losing information?▼

Run the distillation workflow with your source file paths, folder paths, or glob patterns. It extracts every fact, decision, and constraint into dense thematic bullets, then verifies completeness against source headings and named entities before saving the distillate.

What is the difference between a distillate and a summary?▼

A summary is lossy and drops details for readability. A distillate is lossless compression: it preserves every fact, decision, rejected alternative, and constraint while stripping only prose overhead like transitions, hedging, and repeated introductions.

How do I verify a distillate is lossless?▼

Pass the --validate flag to trigger round-trip validation. A separate reconstructor agent rebuilds the source documents from the distillate alone, and the workflow produces a validation report listing any gaps or hallucinations found.

What file formats does document distillation support?▼

The analysis script accepts Markdown, text, YAML, and JSON files. You can provide individual file paths, folders scanned recursively, or glob patterns, and it skips directories like node_modules and .git automatically.

When does the distillate get split into multiple files?▼

Splitting triggers when the estimated distillate exceeds roughly 5,000 tokens or a user-specified token budget requires it. The output becomes a folder with an _index.md orientation file plus self-contained section files organized by semantic topic boundaries.