Skip to content
TrustedSkillsbeta
Back to all skills

Bdd Collaboration

Checked
thebushidocollective·vlatest·testing

This skill facilitates collaborative BDD scenario development by allowing multiple users to simultaneously contribute and refine acceptance tests.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thebushidocollective/han --skill bdd-collaboration -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

thebushidocollective

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned thebushidocollective/han at 19caa51d5f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19caa51d5f
Manifest
plugins/patterns/bdd/skills/bdd-collaboration/SKILL.md
Scanned
1 file, 123 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, BDD Collaboration, facilitates collaborative Behavior-Driven Development (BDD) scenario creation and refinement. It aims to bridge communication between business/product teams, developers, and testers by providing structured techniques for defining acceptance tests and building a shared understanding of requirements. The skill supports "Three Amigos" sessions and utilizes Example Mapping to clarify rules and edge cases.

When to use it

  • When you need to ensure alignment between technical and non-technical stakeholders on software requirements.
  • During the initial stages of a project to collaboratively define acceptance criteria for user stories.
  • To resolve ambiguities or disagreements regarding expected system behavior through structured conversation and example exploration.
  • For refining existing scenarios and identifying potential edge cases that might have been missed.

Key capabilities

  • Three Amigos Sessions: Facilitates sessions involving Product, Development, and Testing perspectives.
  • Example Mapping: Provides a structured technique for clarifying rules with examples and questions (using Yellow, Blue, Green, and Red cards).
  • Discovery Workshop Format: Offers a four-stage process (Introduce, Explore, Document, Review) to guide collaborative scenario development.
  • Ubiquitous Language: Encourages the creation of a shared vocabulary for domain terms within BDD features.

Example prompts

  • "Let's run a Three Amigos session on this user story."
  • "Can we use Example Mapping to clarify the rules around free shipping?"
  • "Walk me through the Discovery Workshop format for defining acceptance criteria."

Tips & gotchas

  • Requires active participation from representatives of Business/Product, Development, and Testing roles.
  • The effectiveness relies on a willingness to engage in open communication and collaborative problem-solving.
  • Familiarity with BDD principles and terminology is helpful for optimal use.