Acceptance design
Acceptance connects the user's outcome to an observable check. Design it before
implementation, and give the worker the exact contract the reviewer will use.
These are operational instructions, not measured failure-rate claims.
Define the experiment
- Name the outcome, affected boundary and scope. Check the command, loader,
artifact or user flow actually affected; a helper test alone may miss the
boundary defect. Identify what the check deliberately leaves untested.
- Name the target host or platform, runner, dependencies, permissions and
inputs. Confirm required source files exist in the delivered base and
travel with the brief. Distinguish existing input paths from files to create.
- Record the exact command, expected observable result and evidence location.
Test that it launches on the target environment before dispatch. Prefer a
repository script when shell quoting or setup would make the command fragile.
Do not depend on an undocumented interpreter or hidden login state.
- Scope every planned write, including tests and generated artifacts. Make
predecessors available in the delivered base, or route the task to a
checkout that contains them. A named branch is not necessarily accessible.
Separate change from preservation
- For a defect or new behavior, demonstrate that the check rejects the old
behavior for the intended reason when feasible. A missing tool or test path
is not that demonstration. If a baseline run is unavailable, state the gap.
- For preservation, establish the existing behavior and require it to remain
valid. Do not demand a failing baseline for behavior meant to stay unchanged.
- Vary meaningful inputs and inspect outputs where the contract depends on
them. A mocked success, repeated implementation constant or file's existence
may prove less than the required outcome. Include relevant regression scope.
- If a worker cannot run a required live-service or platform check, assign it
to a suitable verifier and retain it as required. Local success cannot stand
in for the missing boundary check.
Freeze and correct the contract
Put the exact commands, inputs, preservation requirements and stop conditions
in the brief. Worker and reviewer use the same contract on identified trees.
If the check is wrong or unrunnable, report the mismatch before continuing
dependent work. The task owner records the old and replacement contracts, the
reason and how the replacement still tests the intended outcome. Revalidate
the replacement before resuming; do not silently lower a threshold, remove a
failing case or relabel a failure as success. A changed user requirement is a
scope change to record, not evidence that the old contract passed.
Acceptance is designed when it can distinguish the required outcome from a
plausible failure, runs where assigned, and preserves the agreed boundaries.
1---2name: acceptance-design3description: "Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome."4metadata:5 source: https://skillmd.com/skills/majiayu000/acceptance-design6---78# Acceptance design910Acceptance connects the user's outcome to an observable check. Design it before11implementation, and give the worker the exact contract the reviewer will use.12These are operational instructions, not measured failure-rate claims.1314## Define the experiment15161. Name the outcome, affected boundary and scope. Check the command, loader,17 artifact or user flow actually affected; a helper test alone may miss the18 boundary defect. Identify what the check deliberately leaves untested.192. Name the target host or platform, runner, dependencies, permissions and20 inputs. Confirm required source files exist in the delivered base and21 travel with the brief. Distinguish existing input paths from files to create.223. Record the exact command, expected observable result and evidence location.23 Test that it launches on the target environment before dispatch. Prefer a24 repository script when shell quoting or setup would make the command fragile.25 Do not depend on an undocumented interpreter or hidden login state.264. Scope every planned write, including tests and generated artifacts. Make27 predecessors available in the delivered base, or route the task to a28 checkout that contains them. A named branch is not necessarily accessible.2930## Separate change from preservation3132- For a defect or new behavior, demonstrate that the check rejects the old33 behavior for the intended reason when feasible. A missing tool or test path34 is not that demonstration. If a baseline run is unavailable, state the gap.35- For preservation, establish the existing behavior and require it to remain36 valid. Do not demand a failing baseline for behavior meant to stay unchanged.37- Vary meaningful inputs and inspect outputs where the contract depends on38 them. A mocked success, repeated implementation constant or file's existence39 may prove less than the required outcome. Include relevant regression scope.40- If a worker cannot run a required live-service or platform check, assign it41 to a suitable verifier and retain it as required. Local success cannot stand42 in for the missing boundary check.4344## Freeze and correct the contract4546Put the exact commands, inputs, preservation requirements and stop conditions47in the brief. Worker and reviewer use the same contract on identified trees.48If the check is wrong or unrunnable, report the mismatch before continuing49dependent work. The task owner records the old and replacement contracts, the50reason and how the replacement still tests the intended outcome. Revalidate51the replacement before resuming; do not silently lower a threshold, remove a52failing case or relabel a failure as success. A changed user requirement is a53scope change to record, not evidence that the old contract passed.5455Acceptance is designed when it can distinguish the required outcome from a56plausible failure, runs where assigned, and preserves the agreed boundaries.