ln-42-acceptance-test-builder

Creates and runs reproducible acceptance tests for stated requirements using project-native tooling.

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill ln-42-acceptance-test-builder-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-42-acceptance-test-builder
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/ln-42-acceptance-test-builder
Command: npx skills add https://github.com/ankaboot-source/boucle --skill ln-42-acceptance-test-builder-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack executable proof that stated requirements actually work at the boundaries users and external systems observe. This Skill builds reproducible acceptance tests that produce durable evidence of requirement compliance without touching production code. ## Core Features & Use Cases - Requirement-to-test mapping: Derives expected behavior from requirements, contracts, and independent oracles rather than from the implementation under test. - Project-native execution: Detects the existing test runner, layout, fixtures, and CI invocation so new tests fit the repository's conventions. - Evidence preservation: Records commands, environments, outputs, and first failures, and reports product defects instead of repairing them. - Use Case: After a feature ticket specifies new API behavior, use this Skill to create acceptance tests against a disposable integration environment, run them, and receive a requirements matrix marking each outcome PASS, FAIL, or UNPROVEN. ## Quick Start Create and run acceptance tests for the requirements in this ticket using the repository's existing test runner, and report the verdict with evidence.

Frequently Asked Questions about ln-42-acceptance-test-builder

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

FAQPage Schema
How do I create acceptance tests from written requirements?

Map each requirement to the lowest production-shaped boundary that proves it, such as UI, API, CLI, or durable state. Derive expected behavior from the requirement or an independent contract, then implement tests in the project's existing runner and layout.

What is the difference between acceptance tests and unit tests?

Acceptance tests verify behavior at boundaries users or external systems observe, while unit tests check internal implementation details. This Skill avoids replacing acceptance evidence with unit-level checks of internals absent from the observable contract.

What happens when an acceptance test exposes a product defect?

The Skill stops modifying implementation code, preserves the failing acceptance evidence, and reports the smallest reproduction of the defect. It never repairs production code or weakens assertions to obtain a pass.

Can acceptance tests run against production environments?

No. Tests must never run against production or unapproved external targets. Use disposable integration environments, approved emulators, or repository-defined targets with controlled credentials and data.

How should flaky or nondeterministic test output be handled?

Assert stable invariants and semantic fields instead of snapshotting noise or normalizing away failures. Retries are allowed only to diagnose nondeterminism and must never convert an initial failure into a silent pass.