distill

Extract current code behavior into draft Gherkin feature files.

7|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/kirkchen/beat --skill distill-kirkchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill
Source: https://github.com/kirkchen/beat/tree/main/skills/distill
Command: npx skills add https://github.com/kirkchen/beat --skill distill-kirkchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill helps teams extract the currently implemented behavior from existing code and convert it into draft Gherkin feature files, providing a reliable starting point for Beat adoption without guessing future changes.

Core Features & Use Cases

  • Current-behavior distillation: Generate draft feature files that accurately describe what the code currently does.
  • Beat workflow integration: Artifacts are designed for subsequent verification with /beat:verify and integration into the plan → apply → archive flow.
  • Not for design or exploration: Distill focuses on clarifying existing behavior, not proposing new features or exploring ideas.

Quick Start

Run distill on a target module to generate draft feature files from existing code.

Frequently Asked Questions about distill

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

FAQPage Schema
How do I extract existing behavior into Gherkin feature files?

Distill retroactively adopts BDD by extracting what the code actually does into draft Gherkin features. It targets modules or directories to distill existing behavior, generating feature files without guessing future changes.

Can I generate Gherkin feature files from code that has no tests?

Distill generates draft Gherkin feature files by reading code structure and tests if any are present. It produces feature files and optional design artifacts under beat/changes for retroactive BDD adoption.

Does distill work for designing new features and exploring ideas?

No, distill focuses strictly on clarifying existing behavior rather than proposing new features. It extracts what the code currently does to provide a reliable starting point for BDD adoption without guessing future changes.

What is the best way to verify draft Gherkin features generated from existing code?

The best way to verify draft Gherkin features is using independent verification. Distill artifacts are designed for subsequent verification with /beat:verify and integration into the plan, apply, and archive flow.