Bdd Orchestrator

Orchestrates the full BDD workflow from code to trustworthy business logic — extraction, validation, gap analysis, refinement, acceptance criteria, and test generation. Use when the user requests comprehensive analysis like "understand [feature] from code", "analyze [domain] end-to-end", or "prepare [feature] for implementation or sprint planning", coordinating the other BDD skills step by step.

47 stars 7 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add meirm/reverse-engineering-skill --skill bdd-orchestrator
Manual install
git clone --depth 1 https://github.com/meirm/reverse-engineering-skill.git /tmp/reverse-engineering-skill
mkdir -p ~/.claude/skills
cp -r /tmp/reverse-engineering-skill/skills/bdd-orchestrator ~/.claude/skills/bdd-orchestrator

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# BDD Workflow Orchestrator

You are a BDD workflow orchestrator that coordinates multiple skills to analyze code and produce trustworthy business logic documentation.

## Purpose

When users request comprehensive analysis like "understand [feature] from code" or "analyze [domain] end-to-end," coordinate multiple skills in sequence to:

1. Extract business logic from code
2. Validate BL against implementation
3. Find gaps and ambiguities
4. Refine into deterministic rules
5. Derive acceptance criteria
6. Generate tests

## Workflow

### Step 1: Prerequisites Check

First, check for project configuration:

```yaml
# Check for either:
BDD/project_config.yaml
# or
.cursor/bdd_project_config.yaml
```

If the config exists, read it to understand:
- BL output directory structure (`bl_output.root`)
- BL categories (`bl_output.categories`)
- Domain terminology (`terminology`)
- Code entry points (`entry_points`)

If no config exists:
- Suggest running the `tailor-bdd-skills-for-project` skill first (`/skill:tailor-bdd-skills-for-project`)
- Ask if user wants to proceed with defaults (BL in `business_logic/` with standard categories)
- Verify BL output directory can be created

### Step 2: Extract Business Logic

Run the `reverse-engineering-business-logic` skill: read its SKILL.md and follow it.

```
Target: <user's specified feature, file, or domain>
```

Wait for completion and summarize:
- BL document created with path
- Number of rules extracted
- Code coverage (lines analyzed)
Read the full skill on GitHub

Details

Skill name
bdd-orchestrator
Path
skills/bdd-orchestrator/SKILL.md
License
MIT
Repo updated
2 October 2026

FAQ

What does the Bdd Orchestrator skill do?

Orchestrates the full BDD workflow from code to trustworthy business logic — extraction, validation, gap analysis, refinement, acceptance criteria, and test generation. Use when the user requests comprehensive analysis like "understand [feature] from code", "analyze [domain] end-to-end", or "prepare [feature] for implementation or sprint planning", coordinating the other BDD skills step by step.

How do I install the Bdd Orchestrator skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add meirm/reverse-engineering-skill --skill bdd-orchestrator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Bdd Orchestrator popular?

It lives in meirm/reverse-engineering-skill, which has 47 GitHub stars and 7 forks.

Related skills

Analyze Business Logic Gaps

47

meirm/reverse-engineering-skill

Identifies missing, vague, underspecified, or contradictory business logic within BL documents. Finds incomplete edge cases, missing state transitions, ambiguous terminology, and weak billing rules. Use when reviewing business logic quality, hardening requirements, or preparing BL for implementation.

Marketing, Sales & Business

Derive Acceptance Criteria From Business Logic

47

meirm/reverse-engineering-skill

Converts trusted business logic into product-owner-grade acceptance criteria and developer-ready tasks using Given/When/Then scenarios. Use when creating user stories, preparing for sprints, or turning BL into executable requirements.

Marketing, Sales & Business

Generate Tests From Business Logic

47

meirm/reverse-engineering-skill

Generates scenario tests, rule tests, edge case tests, state transition tests, and billing tests from trusted business logic. Use when creating test suites from BL, ensuring BL coverage, or turning requirements into verifiable tests.

Testing & QA

Game Web2d Specialist

57

AlterLab-IEU/AlterLab_GameForge

Builds 2D browser games with Phaser 4 (primary), PixiJS 8, Kaplay, Excalibur or LittleJS: framework choice, Phaser scenes, Arcade or Matter physics, Tiled/LDtk tilemaps, atlases, pixel-art scaling, Phaser 3 to 4 migration and Playwright checks. Use for "Phaser", "PixiJS", "Kaplay", "2D web game", "tilemap". Not for 3D browser games (use game-threejs-specialist).

Testing & QAIn 1 list

Vibe Testing

24

knot0-com/vibe-testing

This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.

Testing & QAIn 1 list

Game QA Lead

57

AlterLab-IEU/AlterLab_GameForge

QA Lead (Rook Callahan). Writes risk-based test plans, triages bugs, builds regression suites and release gates, and sets up automated tests for Godot (GUT, gdUnit4), Unity, Unreal and web (Vitest, Playwright), including smoke checks for AI-built games. Use for "test plan", "bug triage", "regression", "release gate", "flaky tests". Not for player playtests (use game-playtest).

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.