@tank/idd-bdd-pack

Name: @tank/idd-bdd-pack
Availability: InStock
Author: tankpkg

Map IDD intent layers to BDD Gherkin scenarios and step assertions.

1|1|Updated Feb 20, 2026

Search Tags:#testing #orchestration #bdd #idd #behavior-driven development #intent-driven development

Ready to run

npx skills add https://github.com/tankpkg/skills --skill tank-idd-bdd-pack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: @tank/idd-bdd-pack
Source: https://github.com/tankpkg/skills/tree/main/skills/idd-bdd-pack
Command: npx skills add https://github.com/tankpkg/skills --skill tank-idd-bdd-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between defining software intent and verifying its behavior through end-to-end testing, ensuring that what is intended is what is built and tested.

Core Features & Use Cases

Orchestration: Combines Intent-Driven Development (IDD) with Behavior-Driven Development (BDD) testing.
Workflow Integration: Provides a unified workflow for using .idd/ and .bdd/ directories together.
Traceability: Maps intent layers directly to BDD artifacts for clear verification.
Use Case: When developing a multi-module system, use this pack to ensure that the architectural constraints and user-facing examples defined in your intent files are rigorously tested by your BDD scenarios.

Quick Start

Use the idd-bdd-pack skill to combine your intent files with behavior-driven tests.

Frequently Asked Questions about @tank/idd-bdd-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I unify intent-driven development with behavior-driven testing?▼

To unify intent-driven development with behavior-driven testing, you orchestrate .idd/ and .bdd/ directories together, mapping intent layers like examples and constraints directly to Gherkin scenarios and step assertions for end-to-end verification.

What is intent-driven development orchestration for E2E testing?▼

Intent-driven development orchestration for E2E testing is the process of mapping architectural constraints and user-facing examples defined in intent files to corresponding BDD artifacts, ensuring intent drives tests without mocking.

How do I map .idd/ intent layers to .bdd/ Gherkin scenarios?▼

You map .idd/ intent layers to .bdd/ Gherkin scenarios by orchestrating the integration of intent layers—examples, constraints, and structure—into corresponding BDD artifacts like step assertions and directory layout.

Can I use BDD scenarios to verify multi-module systems without mocking?▼

Yes, you can verify multi-module systems requiring AI-assisted development and E2E verification using BDD scenarios without mocking by ensuring intent drives the tests through the combined .idd/ and .bdd/ directory workflow.

What is the best way to ensure intent drives behavior tests in multi-module systems?▼

The best way to ensure intent drives behavior tests in multi-module systems is to map intent layers directly to BDD artifacts, rigorously testing architectural constraints and user-facing examples defined in your intent files.

Does intent and behavior testing orchestration require mocking for end-to-end verification?▼

No, intent and behavior testing orchestration does not require mocking for end-to-end verification; the approach explicitly ensures that intent drives tests without mocking across multi-module systems.