distill

Classify and summarize project input files into distilled reference documents.

Updated May 24, 2026

Search Tags:#API specification #domain knowledge #structured documentation #feedback triage #requirements distillation #pipeline inputs

Ready to run

npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill distill-rcsnyder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/distill
Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill distill-rcsnyder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill helps convert unstructured or cluttered material in docs/input/ into clean, machine-consumable reference documents so downstream pipeline phases can reliably read and act on consistent artifacts.

Core Features & Use Cases

Source classification & structuring: Extracts requirements, API/integration specs, data schemas, domain knowledge, and feedback from the raw input files.
Additive distilled outputs: Produces concise distilled documents using a distilled- prefix without deleting or modifying the original inputs.
Ambiguity surfacing: Explicitly flags ambiguities, separating verified facts from assumptions and open questions.

Quick Start

Run the distill command with an optional focus area to transform the contents of docs/input/ into distilled- reference documents ready for EXPAND.

Frequently Asked Questions about distill

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

FAQPage Schema

How do I convert messy project briefs and meeting notes into structured documentation?▼

To convert messy project briefs and meeting notes into structured documentation, place raw files in docs/input/. The tool categorizes content like client briefs and feedback, producing concise distilled- reference documents with source attribution for downstream consumption.

What is the best way to structure unstructured API specifications and data schemas for pipeline inputs?▼

Structuring unstructured API specifications and data schemas for pipeline inputs involves reading scattered files and classifying the content. This process extracts domain knowledge and schemas, generating additive distilled- documents that separate verified source-backed facts from assumptions.

How do I separate verified facts from assumptions when triaging scattered feedback?▼

Separating verified facts from assumptions when triaging scattered feedback requires ambiguity surfacing. The tool explicitly flags open questions and distinguishes source-backed information from inferred assumptions in the outputted distilled- reference documents.

Can I generate reference docs from raw inputs without deleting the original files?▼

Yes, you can generate reference docs without deleting original files. The distillation process is additive, creating new documents with a distilled- prefix while preserving and leaving all original raw input materials in docs/input/ completely unmodified.

Does requirements distillation work without external dependencies or components?▼

Requirements distillation works without external dependencies or components. The process operates directly on local input files by reading, categorizing, and summarizing content to produce structured reference documents ready for reliable downstream pipeline phases.