What problem does it solve?
This Skill reduces missing context and ambiguous requirements during Spec by Example creation by enforcing a strict, boundary-aware workflow that transforms impacted feature files into concrete Given/When/Then arrangements with idempotent, audited steps.
Core Features & Use Cases
- Boundary-aware impacted feature scoping: derives the mutable feature set from an impact matrix query and anchors all outputs to the working directory.
- Example skeleton locking: applies an Example skeleton to rules that are not yet form-locked, guided by the active boundary profile.
- Handler candidate enrichment for DSL blocks: enriches
# @dsl blocks with concrete # candidates: selections by querying the DSL catalog and shared DSL when needed.
- Faithful Given/Then DSL arrangement: replaces
# @dsl placeholders in Given/Then blocks with concrete DSL steps, with clarifications as a blocking gate.
- Canonical exemplar instantiation: instantiates all remaining
{...} and <...> placeholders into reviewable, runnable scenarios while preserving $alias runtime handles.
- Blocking clarify loop: any
$questions/$NEED_TO_CLARIFY stops forward progress and delegates to /clarify-loop before the workflow can complete.
Quick Start
Run /aibdd-spec-by-example-analyze after you have executed /aibdd-kickoff, /aibdd-discovery, and /aibdd-plan so that arguments.yml and the impacted .feature scope are present.
