GitHub

nw-acceptance-designer

Authors the public executable oracle when required.

Wave: Other Model: claude-opus-5 Max turns: 40 Tools: Read, Write, Edit, Bash, SendMessage

Commands

Preloaded skills

  • nw-at-completeness-check — Verify that one minimal oracle falsifies every declared delivery obligation without checklist ceremony or duplicate tests.
  • nw-bdd-methodology — BDD patterns for acceptance test design - Given-When-Then as a language-neutral specification style, scenario writing rules, realization in the project's incumbent native scenario syntax (Python pytest-bdd binding labelled), anti-patterns, and living documentation
  • nw-code-analysis-port — KNOWLEDGE — resolve code facts (who-calls-X / where-defined-or-read / call-graph / change-scope / file-atoms) through the vendor-neutral CLI code-fact, degrading LOUD through bundled adapters (AST, TextSearch). Trigger: any time an agent designs, writes, analyzes, or reviews code or tests and needs a structural code fact.
  • nw-distill-prior-wave-reading — Reads and reconciles durable product, architecture, and platform authorities before DISTILL compiles an executable oracle.
  • nw-product-value-slicing — Product-owner foundation for slicing value — elephant carpaccio thin vertical slices, one walking skeleton per feature (not per slice), feature identity from user/product authority, JTBD/domain language framing. Consult when decomposing a feature into independently observable increments.
  • nw-property-based-testing — Load when a design law holds over a broad input, state or sequence domain and needs a generated property test.
  • nw-tdd-methodology-paradigm — Native contract-driven unit and acceptance testing: generative broad laws, finite examples, public-state preservation and real-boundary evidence.
  • nw-tdd-methodology-pbt-deep — Deep property-based-testing mechanics (Hebert) - stateful PBT command-precondition anti-patterns (A13/P6), the four property-finding strategies, the two shrinking mechanisms, and targeted/search-based PBT with its hard limitations
  • nw-tdd-methodology-port-to-port — What a test asserts on and where it enters - port-to-port discipline at all test levels, the layer-specific Universe, refactoring-resilience, and the hexagonal per-layer testing strategy
  • nw-tdd-methodology-test-doubles — Choosing and building a test double - Meszaros taxonomy, classical-vs-mockist verification, the mock-only-at-port-boundaries policy, and the contract that every InMemory double must validate inputs like the real adapter
  • nw-test-design-mandates — Load before writing, reviewing or timing any test - oracle, scenarios, assertions, fakes, names, budgets, walking skeleton.
  • nw-test-design-mandates-composition-contract — Stub - every test rule lives in nw-test-design-mandates; nothing to load here.
  • nw-test-design-mandates-scenario-design — Scenario-design mandates for acceptance tests — Hexagonal Boundary Enforcement (drive through driving ports, never internals), Business Language Abstraction (three abstraction layers), User Journey Completeness, Pure Function Extraction Before Fixtures, Algebraic Analysis Before the Scenario (name the law, find its narrowest surface, declare every gated input, prove the scenario can fail), the 3 Pillars style backbone, and Walking Skeleton Strategy. Consult while shaping or judging a scenario's boundary, language, journey completeness, and fixture strategy. Canonical definitions; SSOT for these mandates.
  • nw-test-organization-conventions — Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
  • nw-typesafe-system-one — Use Jev System One for every supported, authorized semantic judgment when available: relevance selection, handoff preflight, evidence mapping, finding clustering, and confidence-gated escalation.