Menu
Skills in this repository
SkillsMP has collected 109 skills from nWave-ai/nWave-experimental. Open a skill to review its source and details.
nWave-ai/nWave-experimentalShowing 40 of 109 collected skills.
PROCEDURE — validate an EXISTING agent spec against the 19-item checklist. Trigger: checking a spec for compliance (also the shared composition target create/migrate/merge invoke). One job: run the checklist, report pass/fail.
KNOWLEDGE (data) — the 19-item agent-spec validation checklist. The item definitions the validate-spec / todoify procedures RUN against. No sequence of its own.
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Resolve one observed defect through evidence-led RCA, an ATD-owned regression oracle, direct delivery, source-blind EXAMINE when applicable, and one finalization.
Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
Root cause analysis and debugging
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking…
The adversarial-refutation review stance — assume the artifact is WRONG and try to PROVE it, default-to-refuted, diverse lenses, and an exhibited executable counterexample. The shared SSOT every DELIVER review (per-slice C_REVIEWER_AUDIT + per-feature…
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
Comprehensive architecture patterns, methodologies, quality frameworks, and evaluation methods for solution architects. Load when designing system architecture or selecting patterns.
Verify that one minimal oracle falsifies every declared delivery obligation without checklist ceremony or duplicate tests.
Current nWave command map for routing users without teaching retired workflow ceremony.
Evidence-first project reading protocol based on durable authorities, DeliveryContracts, Git, tests, and installed surfaces.
Read-only nWave concierge for methodology, current project evidence, command routing, migration, and troubleshooting.
DDD architect design-time mandates — the Fixture-Fanout Enumeration Mandate for shared-substrate per-caller migration (enumerate production callers plus fixture sites plus atomic bundle scope, mechanically enforced) that both the ddd-architect and its…
Establishes durable deployment, environment, observability, recovery, and CI constraints when platform risk requires the DEVOPS lens.
Tests whether a product problem and opportunity are real, then updates the durable product evidence authorities without creating delivery state.
Port-to-port acceptance criteria + the Architecture of Reference (port-class → test treatment) + the Project Infrastructure Policy (concrete mechanism per port) + the walking-skeleton canonical definition and not-applicable exemptions. Consult while…
Reads and reconciles the durable product, architecture, platform, and delivery authorities before DISTILL compiles an executable oracle and DeliveryContract.
DISTILL RED-ready scaffolding procedure (Mandate 7) — create minimal stub files so ATs are RED (assertion failure, impl missing) not BROKEN (import/infra error), with per-language scaffold recipes, then run the pre-DELIVER fail-for-the-right-reason gate that…
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. Use when the team has a validated problem but hasn't chosen a solution approach.
Authors or reviews one value-side, source-blind expectation charter for a delivery whose validated contract requires EXAMINE.
Core functional programming thinking patterns and type system foundations, language-agnostic
Run an explicit mutation probe over the validated delivery delta, or support the project-level nightly-delta policy. Disabled by default.
Minimizes test count while preserving coverage. Detects byte-identical pairs, parametrize-inflation, language-guarantee tests, AST-shape tests, stale migration nets. Approval gate before any change.
.NET property-based testing with FsCheck, CsCheck, and fsharp-hedgehog frameworks
Erlang/Elixir property-based testing with PropEr, PropCheck, and StreamData frameworks
Go property-based testing with rapid and gopter frameworks
Haskell property-based testing with QuickCheck and Hedgehog frameworks
JVM property-based testing with jqwik, ScalaCheck, and ZIO Test frameworks
Rust property-based testing with proptest, quickcheck, and bolero frameworks
TypeScript/JavaScript property-based testing with fast-check framework and arbitraries
Review dimensions and bug patterns for journey artifact reviews
Runs a timeboxed PROBE to validate one core assumption, then optionally PROMOTES the probe into a walking skeleton committed to the repository. Use when the feature involves a new mechanism, performance requirement, or external integration.
Building and validating a walking skeleton - the WS protocol, per-slice JIT E2E management, Mandate 5 adapter port-class real-I/O treatment (resource table), and Mandate 6 adapter-integration real-I/O requirement
Contract-bound review rules for immutable-oracle integrity, driving-port behavior, test economy, architecture boundaries, and terminal delivery evidence.
Composition-root authoring-contract mandates for acceptance tests — SSOT + Zero Duplication via Types + Services + DSL, Driving-Port-Only Boundary (Farley four-layer protocol-driver contract, fixture-theater/tautological-test anti-pattern), Contract Shape…
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline…
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
Shared routing rules for discovering the earliest missing nWave authority without persistent wizard state.