distill

Document existing software systems by capturing actual behavior and terminology.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/wrteam-jay/blueprint --skill distill-wrteam-jay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint/skills/distill
Command: npx skills add https://github.com/wrteam-jay/blueprint --skill distill-wrteam-jay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the friction caused by tribal knowledge, terminology drift, lack of a shared reference, and the gap between system intent and reality by creating a living specification.

Core Features & Use Cases

  • Capture System Reality: Documents how a system actually works, not just how it was intended.
  • Build Shared Vocabulary: Establishes and enforces consistent terminology across teams.
  • Identify Gaps: Surfaces undocumented decisions, requirements, and stale documentation.
  • Use Case: A new team member needs to understand a complex microservice. They use the distill skill to walk through the service's code and existing documentation, generating a clear blueprint of its functionality, terminology, and key flows.

Quick Start

Use the distill skill to document the existing user authentication system.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I document an existing software system with no up-to-date specifications?▼

To document an existing software system, you analyze its code, existing documentation, and human input to capture actual behavior, producing a living blueprint that serves as a single source of truth for functionality and intent.

What is the best way to establish shared vocabulary and consistent terminology across engineering teams?▼

Establishing shared vocabulary involves analyzing system behavior and existing documentation to identify terminology drift, then generating a unified specification that enforces consistent technical terms across the team.

How can I identify gaps in understanding and undocumented decisions in a legacy microservice?▼

You identify gaps in understanding by cross-referencing actual code behavior with existing documentation and human input, surfacing undocumented decisions, stale documentation, and missing requirements within the microservice.

Can I generate a system specification that reflects actual runtime behavior rather than original intent?▼

Yes, you can generate a system specification reflecting actual runtime behavior by analyzing the code directly, ensuring the resulting living blueprint captures how the system truly operates instead of just its intended design.

Do I need existing technical documentation to perform code analysis and capture system reality?▼

No, you do not need existing technical documentation, although it helps; the code analysis process relies primarily on examining the code and gathering human input to document the system's actual behavior.