aibdd-auto-starter

To generate a walking skeleton, run the AIBDD kickoff to create `.aibdd/arguments.yml`, then invoke the starter generator to dispatch on `STARTER_VARIANT` and produce the correct repo layout. The generator executes deterministically, verifies the variant, and emits a completion report.

Available starter variants for repo scaffolding include `python-e2e`, `java-e2e`, and `nextjs-storybook-cucumber-e2e`. Each variant maps to a specific template family for backend or frontend boundary-aware walking skeletons.

The starter generator applies safe non-overwriting file writes during project setup, skipping any files that already exist. This safety guardrail prevents accidental loss of existing code when generating the walking skeleton.

No, you cannot use the starter generator without the kickoff because it requires `.aibdd/arguments.yml` to exist. The Skill validates argument presence and reads the `STARTER_VARIANT` from this file to dispatch to the correct template.

After walking skeleton generation completes, the Skill performs a variant-specific verification step and emits a structured completion report. This report provides a clear pointer for the next action to run, such as the discovery phase.

No, the starter generator does not modify the AIBDD specifications. It strictly produces the boundary-aware repo layout, verifies the variant, and reports readiness without altering your original spec files.