skills.rest
grimlor
grimlorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bdd-feedback-loop

Convert BDD spec modules into type-clean executable tests with a feedback loop.

2|Updated Mar 5, 2026
Search Tags:#testing#type checking#bdd#spec-first#test implementation#coverage audit#deviation log
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill bdd-feedback-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bdd-feedback-loop
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/bdd-feedback-loop
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill bdd-feedback-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

BDD spec-to-test work often stalls because teams lack a repeatable, safe procedure for converting a behavioral spec into executable tests that are type-checker-clean and self-audited.

Core Features & Use Cases

  • Per-module feedback loop: Turns each BDD spec module into a bounded iteration that reads the spec, discovers the public API, implements tests, validates types, self-audits against BDD principles, logs deviations, and performs a coverage check.
  • Strict spec immutability: Treats the spec as the authoritative input and requires human resolution for genuine spec errors or unresolved deviations.
  • Tautology and boundary discipline: Enforces that “When” invokes production code, that mocks match the declared boundaries, and that assertions reflect SUT behavior rather than hand-constructed expectations.

Use case: You are implementing a new BDD test module for a service and want to ensure the resulting tests follow the spec precisely, fail meaningfully when behavior diverges, and remain aligned with language/toolchain validation rules.

Quick Start

Ask an AI agent to apply the bdd-feedback-loop workflow to implement the next BDD test module from the current spec doc, including type-check validation, self-audit, deviation logging, and a coverage disposition review.

Frequently Asked Questions about bdd-feedback-loop

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

FAQPage Schema
How do I convert BDD spec documents into executable tests?▼

To convert BDD spec documents into executable tests, apply a per-module feedback loop that reads Given/When/Then scenarios, discovers the public API, implements the tests, and validates types. This structured approach ensures your spec-first test implementation yields type-clean test modules.

What is the best way to prevent BDD test tautology when implementing spec scenarios?▼

Preventing BDD test tautology requires enforcing boundary discipline to ensure "When" steps invoke production code and that assertions reflect System Under Test (SUT) behavior rather than hand-constructed expectations. This keeps tests meaningful and prevents self-fulfilling prophecies.

How do I handle spec errors or unresolved deviations during BDD test implementation?▼

Handle spec errors or unresolved deviations by logging them in a deviation log rather than altering the original spec. This approach enforces strict spec immutability, treating the spec as authoritative and requiring human resolution for genuine discrepancies.

Does the BDD feedback loop process support different languages and toolchains?▼

Yes, the BDD feedback loop supports any language or toolchain by using language references to guide validation commands. It applies a disciplined per-module iteration to ensure type-checking compliance across diverse development environments.

How do I audit test coverage gaps when implementing Given/When/Then scenarios?▼

Audit test coverage gaps by performing a coverage-gap disposition triage at the end of the feedback loop. This process evaluates implemented tests against the BDD spec to identify and triage missing scenarios or behavioral coverage deficiencies.

Why do my BDD tests fail type-checking even when the behavior matches the spec?▼

BDD tests may fail type-checking if the public API discovery missed type definitions or if mocks do not match declared boundaries. Validating types through language-specific commands within a feedback loop ensures the test modules remain type-clean.

Related Skills

Explore More Software Engineering Skills→
tikazyqtikazyq
5

bdd-scenario-quality-check

Validate BDD scenarios for Given-When-Then format and CRAFT standards.

Community
Intermediate
tech-with-sethtech-with-seth
4

create-unit-test

Create Vitest unit tests co-located with source files using project templates.

Official
Intermediate
matteocervellimatteocervelli
25

coverage-analyzer

Analyze test coverage gaps and validate thresholds with pytest-cov.

Community
Advanced
dogganidhaldogganidhal
43

generate-tests

Generate vitest test cases from spec Test Scenarios headings.

Community
Advanced