agentsclimarketplace
Sign in

Testing bdd

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-bdd

Behavior-driven scenario design for shared business language and executable acceptance evidence. Use when teams must align on Given-When-Then scenarios before implementation sign-off or release; do not use for performance benchmarking or deployment policy design.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill testing-bdd

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

One thing to look at

  • 0 stars0 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.

SKILL.md

2.1 KB, 356 tokens by cl100k_base, as published. Nobody here has run it

Testing BDD

Overview

Use this skill to encode requirement intent as executable behavior scenarios that product, QA, and engineering can all review.

Scope Boundaries

  • Use when behavior semantics need alignment across stakeholders before or during implementation.
  • Typical requests:
    • Turn ambiguous requirements into Given-When-Then scenarios.
    • Align PO, QA, and engineering on acceptance behavior.
    • Define executable acceptance evidence before release.
  • Do not use when:
    • The primary task is load/performance benchmark design (performance-*).
    • The task is operational monitoring/alert policy (observability-*).

Inputs

  • Requirement candidates and acceptance concerns
  • Domain language and business rules
  • Existing test policy and release constraints

Outputs

  • Scenario suite in Given-When-Then format with requirement mapping
  • Decision record describing scenario strategy and assumptions
  • Verification checklist with pass/fail signals

Workflow

  1. Clarify behavior decisions and non-negotiable constraints.
  2. Model happy-path, alternate, and failure behavior in ubiquitous language.
  3. Compare scenario granularity options and choose one with rationale.
  4. Make scenarios executable and traceable to acceptance decisions.
  5. Publish residual risks and unresolved semantic disputes.

Quality Gates

  • Scenarios are understandable by non-engineering stakeholders.
  • Acceptance semantics are explicit and testable.
  • Assumptions and confidence are documented.
  • Evidence is reproducible and linked to requirements.

Failure Handling

  • Stop when critical behavior cannot be expressed unambiguously.
  • Escalate when stakeholder interpretations remain incompatible.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. 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.