aibdd-auto-starter

What problem does it solve?

Starting a new AIBDD project often stalls because the system needs the right starter skeleton, correct variant, and the expected repo layout before any real discovery or implementation can begin.

Core Features & Use Cases

• Walking skeleton generation from kickoff arguments: Creates the initial backend or frontend structure using the arguments.yml-declared STARTER_VARIANT.
• Variant dispatch (frontend vs backend): Routes to one of python-e2e, java-e2e, or nextjs-storybook-cucumber-e2e, mapping each to its correct template family.
• Safety guardrails: Verifies arguments presence and starter templates existence; skips overwriting files when they already exist; performs a variant-specific verification step and reports readiness.
• Next-step reporting for AIBDD flow: Emits a structured completion report and a clear pointer for what to run next (e.g., discovery).

Quick Start

Run the AIBDD kickoff first to produce .aibdd/arguments.yml, then invoke aibdd-auto-starter so it generates the correct walking skeleton based on STARTER_VARIANT in that arguments file.