agentsclimarketplace

Derive tests

Skill teklabsdigital/x2-method/skills/derive-tests

AI builds faster than anyone, with no skin in the game and no memory of yesterday. How do you govern that? With X2, decisions stay in files people own, unbreakable rules fail the build, code is disposable, and every human turn is counted. Done is an audited report, never the agent's word.

Install
npx -y skills add teklabsdigital/x2-method --skill derive-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use only after the lock (gate 2b) is on record for the slice portion, to derive the fidelity ledger and acceptance scenarios from the locked prototype. Triggers when a portion is newly locked or re-locked. Never use before the lock, and never use it to hand-author prototype-fidelity test cases from prose.

SKILL.md

2.9 KB, as published. Nobody here has run it

X2 Derive Tests

Turn the locked portion into its tests. Nothing here is authored from imagination: the locked prototype is the acceptance contract, and the tests are projections of it.

What derives from the lock

  • The per-slice fidelity ledger (design/ledger/slice-NNN.md): the locked portion's visual atoms, enumerated. The kernel tests it in both directions: every ledger atom renders (exhaustiveness) and nothing renders beyond the ledger (de-fabrication). Until the prototype-to-ledger exporter exists (owed on the claim), the hand-derived ledger is a known second-source risk: derive it at lock time only, from the artifact on disk, never maintain it by hand alongside a moving prototype.
  • The acceptance scenarios on the e2e floor: the flows the locked portion shows, driven through the real client services against a running server.

The scoping of "no hand-authored test cases"

The ban is precise, per the record's wording fix:

  • Banned: authoring prototype-fidelity tests ahead of the lock. They derive from it.
  • Not banned: claim-driven tests: harness scenarios, gate tests, guard tests. These keep the write-it-first, watch-it-fail shape, and they did the most catching in the pilot.

Coverage expectations the exit report will check

Derivation should leave these satisfiable, because slice-exit reports them:

  • Every public method of every client data service has at least one harness scenario through the real transport, and when the product owns identity, the harness exercises the real sign-in path at least once; minting around auth is setup for other scenarios, never a substitute (INV-10, ruled: the gated harness profile makes this achievable).
  • A composed-app smoke exists per primary flow: the actual entrypoint, at least one real request (INV-07).
  • A service method with no surface in the locked portion is a sanctioned UI-unsurfaced state when it is e2e-covered and its boundary is documented (CONF-03). It is never resolved by inventing UI the prototype does not contain; the fidelity tests would fail that fabrication, and they should.

One discipline line

Prove a derived suite can fail: write one assertion wrong, watch it fail, fix it. A suite that cannot fail is not evidence.

Human-turn contract

  • No gate of its own. A gap between the locked portion and what is derivable is a record-gap question for the human, never an invented criterion.

What this skill must NOT produce

  • Nothing before the lock is on record.
  • No criteria the prototype does not show, no edits to the prototype or ledger direction, no implementation code.

Next

implement.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.