walden-testability

Installation
SKILL.md

Walden Testability

Use this skill to settle what each proof will cost while the design is still being written. A proof is cheap when the design lets it provoke the condition a criterion names and see the response from outside. When the design does not, the proof becomes slow, flaky, end-to-end only or impossible, and an agent working in a loop learns to work around it instead of fixing the code.

For every acceptance criterion this skill asks whether a proof can provoke the condition its EARS clauses name (controllability), see the response its SHALL names from outside (observability), decide pass or fail against an oracle the implementation did not produce, and run inside the agent's loop. It answers with the cheapest sufficient proof and the seams the design must provide.

The walden skill authors the present, walden-history reads the past, and this skill makes the promised provable. It advises the design; it never advances the workflow. Reply in the user's preferred language.

When To Use

  • The user asks for a testability or verifiability review of a Walden design, or of one feature's acceptance criteria.
  • The user asks how a criterion can be proven, which proof it needs, or what that proof will cost.
  • Controllability, observability, oracles, flaky or slow proofs, or design for testability come up while a design is being drafted.

Do not use it to author requirements, design or tasks, to open or approve a review, or to write or run tests: that is the walden skill.

Prerequisites

Installs
9
GitHub Stars
62
First Seen
12 days ago