bmad-distillator

Distill source documents into lossless, LLM-optimized bullet-only distillates.

Updated May 3, 2026
One-click install
npx skills add https://github.com/tabesink/deepdoc-agent --skill bmad-distillator-tabesink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-distillator
Source: https://github.com/tabesink/deepdoc-agent/tree/main/.cursor/skills/bmad-distillator
Command: npx skills add https://github.com/tabesink/deepdoc-agent --skill bmad-distillator-tabesink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of turning large, human-oriented documents into hyper-compressed, token-efficient distillates that preserve every fact while staying optimized for downstream LLM workflows.

Core Features & Use Cases

  • Lossless document distillation: Removes overhead while preserving every decision, constraint, relationship, and fact for downstream consumption.
  • Router-driven workflow: Uses analysis to determine whether to produce a single distillate or semantically split sections.
  • Structured, verification-friendly output: Produces a bullet-only distillate format with ## theme headings and optional split-folder layout.
  • Optional round-trip validation: Reconstructs sources from the distillate and reports gaps/hallucinations when subagent spawning is available.

Quick Start

Ask the AI to distill the provided documents into a lossless distillate with a target token budget and save it next to the primary source.

Frequently Asked Questions about bmad-distillator

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

FAQPage Schema
How do I compress large documents for LLM context optimization without losing facts?

You can compress large documents for LLM context optimization by distilling them into a bullet-only format. This lossless compression preserves all decisions, constraints, and relationships while removing prose overhead for downstream workflows.

What is semantic splitting for token budgeting in document distillation?

Semantic splitting for token budgeting divides source documents into section-specific distillates within a split-folder layout. It analyzes sources to route content into manageable chunks that fit target token limits while maintaining structural integrity.

How does round-trip validation verify lossless document compression?

Round-trip validation verifies lossless document compression by using a reconstructor subagent to rebuild the original sources from the distilled output. It then reports any gaps or hallucinations to ensure factual completeness.

Can I distill multiple source documents into a single LLM-optimized distillate?

Yes, you can distill multiple source documents into a single LLM-optimized distillate. The router-driven workflow analyzes the sources to determine whether to produce one unified file or semantically split sections.

What are the limitations of using a bullets-only format for information extraction?

The bullets-only format for information extraction removes all narrative prose, which limits readability for humans. It is strictly designed for LLM context optimization and requires YAML frontmatter to structure the extracted facts and themes.

When do I need document distillation for LLM workflows?

You need document distillation for LLM workflows when human-oriented source documents are too large for target token budgets. It hyper-compresses text into structured facts and decisions while preparing the output for downstream consumption.