nw-distill

Create acceptance tests within the DISTILL wave using SSOT artifacts and driving-port verification.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-distill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-distill
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-distill
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-distill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured methodology for creating acceptance tests within the DISTILL wave. It encapsulates domain knowledge for acceptance designers, including port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.

Core Features & Use Cases

  • Port-to-Port Principle: Every acceptance criterion must name the driving port through which behavior is exercised, enabling tests that are wired to actual system entry points.
  • Prior Wave Reading: Before scenario writing, read SSOT and feature delta artifacts to align expectations with upstream decisions.
  • Artifact Reconciliation: Reconcile wave decisions across DISCUSS, DESIGN, and DEVOPS artifacts to avoid contradictions.
  • Walking Skeleton Strategy: Decide and document walking skeleton strategy, auto-detect adapters, and map them to real or in-memory I/O as appropriate.
  • Driving Adapter Verification: Ensure driving adapters are exercised via subprocess/HTTP/hook in at least one walking skeleton scenario.
  • Documentation Back-Propagation: Record upstream findings and decisions in docs/feature/{feature-id}/distill/upstream-issues.md when gaps or contradictions are discovered.

Quick Start

Start by gathering SSOT artifacts and identifying driving ports before writing the first set of acceptance-scenario sketches.

Frequently Asked Questions about nw-distill

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

FAQPage Schema
What is the port-to-port principle in acceptance test design?

The port-to-port principle requires every acceptance criterion to name the driving port through which behavior is exercised, ensuring tests are wired directly to actual system entry points. This alignment enables precise walking-skeleton verification.

How do I reconcile wave decisions across DISCUSS, DESIGN, and DEVOPS artifacts?

Artifact reconciliation avoids contradictions by reading SSOT and feature delta artifacts before scenario writing. You record upstream findings and decisions in docs/feature/{feature-id}/distill/upstream-issues.md when gaps or contradictions are discovered.

How do I plan a walking skeleton strategy for driving adapter verification?

Plan a walking skeleton strategy by auto-detecting adapters and mapping them to real or in-memory I/O. Ensure driving adapters are exercised via subprocess, HTTP, or hook in at least one walking skeleton scenario.

When should I document back-propagation in distill upstream issues?

Document back-propagation in upstream-issues.md when gaps or contradictions are discovered during prior wave reading. This occurs when reconciling wave decisions across DISCUSS, DESIGN, and DEVOPS artifacts against the SSOT.

Does acceptance test scenario governance require frontmatter-driven discovery?

Yes, acceptance test scenario governance requires frontmatter-driven discovery within the DISTILL wave. This structured methodology ensures scenario governance and artifact reconciliation are satisfied across all driving-port verifications.