forward-derivation

To generate BDD scenarios from specifications, you provide an approved SDD spec and run the derivation command, which parses the file to produce Gherkin features with a 1:1 mapping to your acceptance criteria.

Yes, you can create TDD test skeletons from acceptance criteria by running the derivation command on an approved spec, which generates code skeletons with TODO placeholders directly aligned to each criterion.

The best way to ensure traceability is using forward-derivation, which enforces an explicit 1:1 mapping between every acceptance criterion and its generated BDD scenarios or TDD skeletons, complete with source attribution.

To generate ATDD tables alongside BDD features and TDD skeletons, you run the full derivation command, which optionally produces acceptance test tables from your approved SDD specifications during the derivation workflow.

Yes, you need a fully approved SDD specification before deriving Gherkin scenarios, because the derivation process validates the spec structure and relies on finalized acceptance criteria to maintain accurate source attribution.

During test generation, if your specification structure is invalid, the SPEC parsing stage will fail to extract the acceptance criteria properly, preventing the derivation of BDD scenarios and TDD skeletons until the spec is corrected.