gitnexus-bddlisted

# BDD Scenarios for Pickle-Dot Auto-Patterns ## When to Use - Authoring new Given/When/Then scenarios for pickle-dot builder auto-patterns - Reviewing existing scenarios against current `dot-builder.ts` behavior - Cross-checking whether a builder change breaks documented pattern contracts - Generating scenarios from the pipeline-author perspective for a new opt-in feature ## Reference Material Three coordinated BDD scenario artifacts describe the builder's auto-pattern behavior: | File | Format | Perspective | |---|---|---| | `prds/bdd-scenarios-auto-patterns.md` | Markdown | Implementation detail (node attrs, builder internals) | | `.claude/bdd-scenarios/auto-patterns.md` | Markdown | Pipeline author (observable behavior) | | `.claude/skills/gitnexus/gitnexus-bdd/scenarios/pickle-dot-auto-patterns.feature` | Gherkin `.feature` | Machine-readable, pipeline author | Always reconcile all three when modifying scenarios — drift between them hides builder regressions. ## Workflow ``` 1. READ the relevant PRD in prds/ (source of truth for what the pattern does) 2. READ the current scenario files (all three above) 3. READ extension/src/services/dot-builder.ts to find the pattern's emission code 4. WRITE the scenario in all three formats if adding new, or update each if changing 5. VERIFY by tracing a sample BuilderSpec through the pattern mentally ``` ## Scenario Authoring Conventions - **Pattern numbering**: Match the builder's `patternsApplied` set (0a, 0b, 0c, ..., 1, 2