Use when facilitating BDD collaboration between developers, testers, and business stakeholders. Use when running discovery workshops and example mapping sessions.
Facilitates BDD collaboration sessions including Three Amigos meetings and Example Mapping workshops. Use this when you need to align developers, testers, and business stakeholders on shared requirements and acceptance criteria through structured discovery conversations.
/plugin marketplace add TheBushidoCollective/han/plugin install jutsu-bdd@hanThis skill is limited to using the following tools:
Master the collaborative aspects of Behavior-Driven Development to bridge communication between technical and business teams.
The Three Amigos brings together three perspectives:
Session Structure:
1. Product Owner presents the user story
2. Developer asks clarifying questions
3. Tester identifies potential edge cases
4. Team writes scenarios together
5. Everyone agrees on acceptance criteria
Example Mapping is a structured conversation technique:
┌─────────────────────────────────────────┐
│ STORY: As a customer, I want to... │ (Yellow card)
├─────────────────────────────────────────┤
│ RULE: Orders over $50 get free shipping │ (Blue card)
│ ├── Example: $60 order = free │ (Green card)
│ ├── Example: $49 order = $5 shipping │ (Green card)
│ └── Question: What about $50 exactly? │ (Red card)
├─────────────────────────────────────────┤
│ RULE: Express shipping always costs $15 │ (Blue card)
│ ├── Example: $100 order express = $15 │ (Green card)
│ └── Example: $30 order express = $15 │ (Green card)
└─────────────────────────────────────────┘
1. INTRODUCE (5 min)
- Present the feature or story
- Share any existing context
2. EXPLORE (20 min)
- "What are the rules?"
- "Can you give me an example?"
- "What could go wrong?"
3. DOCUMENT (15 min)
- Write scenarios together
- Capture questions for later
4. REVIEW (10 min)
- Read scenarios aloud
- Confirm shared understanding
Build a shared vocabulary:
# Domain terms defined clearly
Feature: Subscription Management
# Define terms in feature description
A "subscriber" is a customer with an active subscription.
A "churned subscriber" has cancelled within the last 30 days.
"Winback" is re-activating a churned subscriber.
Scenario: Winback offer for churned subscriber
Given a churned subscriber from 15 days ago
When they visit the pricing page
Then they should see the winback offer
Feature: Payment Processing
# Link to business documentation
@jira:PAY-123
@confluence:payment-rules
# Version tracking
@since:v2.1
Scenario: Process credit card payment
# This scenario documents the current behavior
# Last verified: 2024-01-15
Use bdd-collaboration when you need to:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.