scaffold-archipy-bddlisted

# Scaffold ArchiPy BDD ## Before writing files 1. Inspect existing `features/`, Behave config, scenario context, tags, containers, and the behavior being tested. 2. Infer naming and reuse shared support files. Ask only for an unresolved feature name or whether real infrastructure is required; default to mocks. 3. Never overwrite shared support files. Merge missing hooks/registrations while preserving project-specific behavior. ## Prefer ArchiPy ```bash uv add "archipy[behave]" # infra mode also: uv add "archipy[testcontainers]" ``` ## Generate Under **project root** (create shared files only if missing): ```text features/ ├── <name>.feature ├── steps/ │ └── <name>_steps.py ├── scenario_context.py # always — adapt from ArchiPy pattern ├── scenario_context_pool_manager.py # always — Singleton pool ├── environment.py # always — behave hooks ├── test_helpers.py # always — get_current_scenario_context └── test_containers.py # infra mode only — ContainerManager + needed containers .env.test # infra mode — REDIS__IMAGE, POSTGRES__IMAGE, … ``` Model after ArchiPy `features/` + docs tutorial (consumer-slim — no library gRPC/Temporal special cases unless the app needs them). Resolve files under `reference/` relative to this `SKILL.md` in the plugin installation (`$CURSOR_PLUGIN_ROOT/skills/scaffold-archipy-bdd/` or `$CLAUDE_PLUGIN_ROOT/skills/scaffold-archipy-bdd/`). These are plugin