@scemoon/cdh 1.0.5 → 1.0.7

package/ai-dlc-skill/phases/understand/lifecycle.md

@@ -1,184 +0,0 @@
-# AI-DLC Phase 1: Understand (理解)
-
-Transform business intent into formal specification and behavior scenarios, scoped to the right FR namespace.
-
-## Goal
-
-Convert a business need into unambiguous, verifiable requirements before any design or code work begins. For multi-component features, capture the **cross-component boundary** in addition to per-component behavior.
-
-## Flow
-
-```
-Intent (business need / user story)
-  │
-  ▼
-Identify scope: which components does this touch?
-  │
-  ▼
-SDD: Proposal (why, what, impact, affects: [native|desktop|web|backend|wxa|mya|tta|contracts])
-  │
-  ▼
-SDD: Spec Delta (EARS format — ADDED/MODIFIED/REMOVED, FR namespaces)
-  │
-  ▼
-BDD: Feature Files
-  - features/{component}/{domain}/{feature}.feature   (per-component)
-  - aidlc/features/cross-stack/{domain}/{feature}.feature   (full flow, if applies)
-  │
-  ▼
-Gate: Human review → approved or revise
-```
-
-## Scope Identification
-
-Before writing the spec, declare which components the feature affects. This determines the FR namespaces and which lifecycle paths run.
-
-| Affects | Example | FRs |
-|---------|---------|-----|
-| `[backend]` only | Internal API | `BE-FR-NNN` |
-| `[web, backend]` | Login UI + API | `WEB-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[native, backend]` | Native login | `NATIVE-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[desktop, backend]` | Desktop login | `DESKTOP-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[wxa, backend]` | Mini-program login | `WXA-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[mya, backend]` | Mini-program login | `MYA-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[tta, backend]` | Mini-program login | `TTA-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[web, native, desktop, wxa, mya, tta, backend]` | Full feature | `WEB-FR-NNN`, `NATIVE-FR-NNN`, `DESKTOP-FR-NNN`, `WXA-FR-NNN`, `MYA-FR-NNN`, `TTA-FR-NNN`, `BE-FR-NNN`, `INT-FR-NNN` |
-| `[contracts]` | Schema-only change | `INT-FR-NNN` only |
-
-`affects: [contracts]` is reserved for **pure contract changes** (e.g. add a new field shared by all components). It still requires Plan + Verify.
-
-## SDD — Spec-Driven Development
-
-### Intent Capture
-
-```markdown
-## Intent
-
-**Title:** {{title}}
-**Affects:** [{{components}}]
-**Why:** {{why}}
-**What:** {{what}}
-**Success:** {{success_criteria}}
-```
-
-### Spec Delta (EARS) with Namespace
-
-```markdown
-## Change: CHG-{{id}} — {{title}}
-
-**Affects:** [{{components}}]
-**Contracts touched:** {{list or "none"}}
-
-## ADDED Requirements
-
-### INT-FR-{{nnn}}: {{contract_title}}
-(only if affects contracts or ≥2 components)
-
-**Description (Event-Driven):**
-When a {{event}}, the system SHALL {{behavior}} on the contract boundary.
-
-### BE-FR-{{nnn}}: {{backend_title}}
-**Description (Event-Driven):**
-When {{event}}, the backend SHALL {{behavior}}.
-
-### WEB-FR-{{nnn}}: {{web_title}}
-**Description (Event-Driven):**
-When {{event}}, the web client SHALL {{behavior}}.
-
-### NATIVE-FR-{{nnn}}: {{native_title}}
-**Description (Event-Driven):**
-When {{event}}, the native client SHALL {{behavior}}.
-
-### DESKTOP-FR-{{nnn}}: {{desktop_title}}
-**Description (Event-Driven):**
-When {{event}}, the desktop client SHALL {{behavior}}.
-
-### WXA-FR-{{nnn}}: {{wxa_title}}
-**Description (Event-Driven):**
-When {{event}}, the WeChat Mini Program SHALL {{behavior}}.
-
-### MYA-FR-{{nnn}}: {{mya_title}}
-**Description (Event-Driven):**
-When {{event}}, the Mini Program SHALL {{behavior}}.
-
-### TTA-FR-{{nnn}}: {{tta_title}}
-**Description (Event-Driven):**
-When {{event}}, the TikTok Mini Program SHALL {{behavior}}.
-```
-
-### EARS Patterns
-
-| Pattern | Syntax | When to Use |
-|---------|--------|-------------|
-| Ubiquitous | `The system SHALL ...` | Always-active rules |
-| Event-Driven | `When {event}, the system SHALL ...` | Trigger-based behavior |
-| State-Driven | `While {state}, the system SHALL ...` | Active state conditions |
-| Unwanted | `If {condition}, the system SHALL ...` | Error handling |
-| Optional | `Where {feature} enabled, the system SHALL ...` | Feature flags |
-
-## BDD — Behavior-Driven Development
-
-### Per-Component Feature Files
-
-```gherkin
-@WEB-FR-001
-Feature: Web Login UI
-
-  @WEB-FR-001 @positive
-  Scenario: User logs in successfully
-    Given the web app is on the login page
-    When the user submits valid credentials
-    Then the user is redirected to dashboard
-    And the user receives a JWT in storage
-
-  @WEB-FR-001 @negative
-  Scenario: Invalid credentials show error
-    ...
-
-  @WEB-FR-001 @edge
-  Scenario: Empty fields show validation
-    ...
-```
-
-### Cross-Stack Feature File (mandatory for `affects ≥ 2 components`)
-
-```gherkin
-@INT-FR-001
-Feature: Cross-stack login flow
-
-  @INT-FR-001 @positive
-  Scenario: Web login reaches backend and stores token
-    Given the web app is on the login page
-    When the user submits valid credentials
-    Then the backend POST /auth/login returns 200 with JWT
-    And the web app stores the token
-    And the user is redirected to dashboard
-
-  @INT-FR-001 @negative
-  Scenario: Backend rejects invalid credentials with 401
-    ...
-
-  @INT-FR-001 @edge
-  Scenario: Backend timeout surfaces a user-friendly error
-    ...
-```
-
-## Artifacts
-
-| Artifact | Location | Purpose |
-|----------|----------|---------|
-| Intent | `aidlc/requirements.md` | Business need + `affects` |
-| Spec delta | `aidlc/openspec/changes/{id}/spec-delta.md` | EARS, FR namespaces, `affects` |
-| Per-component BDD | `apps/{component}/features/{domain}/{feature}.feature` | Component behavior |
-| Cross-stack BDD | `aidlc/features/cross-stack/{domain}/{feature}.feature` | End-to-end flow |
-| Contract spec | `aidlc/contracts/{api,events}/{name}.{yaml,graphql}` | INT-FR-NNN source of truth |
-
-## Gate
-
-**Before advancing to Plan phase:**
-- [ ] `affects: [...]` declared in spec-delta
-- [ ] Spec delta uses EARS format
-- [ ] Per-component FRs: each tagged `@FR-{PREFIX}-NNN` (e.g. `@NATIVE-`, `@DESKTOP-`, `@WEB-`, `@BE-`, `@WXA-`, `@MYA-`, `@TTA-`), ≥3 scenarios (positive/negative/edge)
-- [ ] If `affects` includes ≥2 components: at least one `INT-FR-NNN` and a `aidlc/features/cross-stack/*.feature` with ≥3 scenarios
-- [ ] If `affects` includes contracts: contract file present in `aidlc/contracts/`
-- [ ] Human reviewed and approved

package/ai-dlc-skill/phases/understand/prompt.md

@@ -1,41 +0,0 @@
-# Understand Phase Agent Prompt
-
-你是一个 AI-DLC Understand Phase Agent。
-由 Master Agent 委派处理需求分析。
-
-## 输入
-- Intent 描述（来自用户 / Master）
-- `affects: [component list]` 声明
-
-## 任务
-
-1. **SDD: Intent Capture**
-   - 在 `aidlc/requirements.md` 记录 Why / What / Success Criteria / Scope
-   - 声明 `affects: [native|desktop|web|backend|wxa|mya|tta|contracts]`
-
-2. **SDD: Spec Delta (EARS)**
-   - 在 `aidlc/openspec/changes/{id}/spec-delta.md` 输出
-   - 使用 EARS 格式：Ubiquitous / Event-Driven / State-Driven / Unwanted / Optional
-   - FR 必须使用命名空间前缀（BE-FR-001, WEB-FR-001 等）
-
-3. **BDD: Feature Files**
-   - 每个 FR ≥3 个 scenario（positive / negative / edge）
-   - Per-component: `apps/{component}/features/{domain}/{feature}.feature`
-   - Cross-stack: `aidlc/features/cross-stack/{domain}/{feature}.feature`
-   - Tag 使用 `@FR-PREFIX-NNN`
-
-4. **Contract First**（跨组件时）
-   - 在 `aidlc/contracts/{api,events}/` 创建合约文件
-   - 引用 INT-FR-NNN
-
-## 输出产物
-- `aidlc/requirements.md`
-- `aidlc/openspec/changes/{id}/spec-delta.md`
-- `apps/{component}/features/{domain}/{feature}.feature`
-- `aidlc/features/cross-stack/{domain}/{feature}.feature`（跨组件时）
-- `aidlc/contracts/{api,events}/{name}.yaml`（跨组件时）
-
-## 约束
-- 遵守 `rules.md` 中的 UND-001 到 UND-006
-- 遵守 `core/security.md`
-- 完成前必须通过 Human Gate 审查

package/ai-dlc-skill/phases/understand/rules.md

@@ -1,37 +0,0 @@
-# Understand Rules (UND-*)
-
-## UND-001: Intent Documentation
-**Severity:** MUST
-**Description:** Before any specification or implementation, the business intent MUST be documented. Intent includes: what is being built, why, and how success is measured.
-**Valid:** Intent captured in `aidlc/requirements.md` with `affects: [...]` before spec delta.
-**Invalid:** Starting spec delta or feature files without documented intent or without an `affects` declaration.
-
-## UND-002: EARS Format
-**Severity:** MUST
-**Description:** All functional requirements MUST use EARS syntax (Ubiquitous, Event-Driven, State-Driven, Unwanted, or Optional).
-**Valid:** `When a user submits valid credentials, the system SHALL return a JWT token.`
-**Invalid:** `The login should work well and be fast.`
-
-## UND-003: BDD Scenario Coverage
-**Severity:** MUST
-**Description:** Each functional requirement MUST have at least 3 BDD scenarios covering positive, negative, and edge cases. Scenarios MUST be tagged with the FR namespace prefix (`@NATIVE-`, `@DESKTOP-`, `@WEB-`, `@BE-`, `@WXA-`, `@MYA-`, `@TTA-`, or `@INT-`).
-**Valid:** `@WEB-FR-001 @positive` with three scenarios per FR.
-**Invalid:** One scenario per FR, or missing namespace prefix.
-
-## UND-004: Affects Declaration
-**Severity:** MUST
-**Description:** Every spec delta MUST declare `affects: [native, desktop, web, backend, wxa, mya, tta, contracts]`.
-**Valid:** `## Change: CHG-001 — User Login\nAffects: [web, backend, contracts]`
-**Invalid:** Spec delta without an `affects` declaration.
-
-## UND-005: Cross-Component Feature Decomposition
-**Severity:** MUST
-**Description:** A feature that affects ≥2 components MUST be split into: one FR per component, one or more `INT-*` FRs, and a `aidlc/features/cross-stack/*.feature` file.
-**Valid:** `affects: [web, backend]` → `WEB-FR-001`, `BE-FR-001`, `INT-FR-001`, plus cross-stack feature file.
-**Invalid:** A single feature file claiming to test both web and backend behavior.
-
-## UND-006: Contract-First for Cross-Component
-**Severity:** MUST
-**Description:** When a feature introduces or changes a public API or event consumed by another component, a contract file MUST be added or updated in `aidlc/contracts/` before any per-component implementation.
-**Valid:** `aidlc/contracts/api/auth.yaml` defines `POST /auth/login` before any code.
-**Invalid:** Per-component code that depends on a contract not in `aidlc/contracts/`.

package/ai-dlc-skill/phases/verify/entry.md

@@ -1,26 +0,0 @@
----
-name: ai-dlc-verify
-description: "Verify Phase: TDD Red-Green-Refactor → Contract Test → Quality Gates"
-triggers:
-  - verify
-  - TDD
-  - test
-  - quality-gate
----
-
-# Verify Phase (验证)
-
-Execute TDD per BDD scenario, verify contracts, enforce quality gates.
-
-## Entry
-
-See `lifecycle.md` for the full phase flow.
-See `rules.md` for enforceable rules (VRF-001 to VRF-006 + INT-001 to INT-006).
-See `prompt.md` for the sub-agent delegation prompt template.
-
-## 当被委派时
-
-1. 按 DAG 顺序对每个 unit 执行 TDD Red→Green→Refactor
-2. 运行合约测试 + 检查 backward-compat
-3. 运行 cross-stack e2e
-4. 执行质量门禁（cov≥80%, 0 vulns, no TODO）

package/ai-dlc-skill/phases/verify/lifecycle.md

@@ -1,192 +0,0 @@
-# AI-DLC Phase 3: Verify (验证)
-
-Execute TDD red-green-refactor per BDD scenario at the right test layer, verify all scenarios, and run cross-component contract and cross-stack gates.
-
-## Goal
-
-Ensure every BDD scenario is correctly implemented at the right layer, every contract is backward-compatible, and the full stack e2e flow works — before delivery.
-
-## Flow
-
-```
-Plan + Tasks approved
-  │
-  ▼
-For each unit in DAG order (within each affected component):
-  For each BDD scenario in unit:
-    │
-    RED:   Write test at the right layer → confirm failure
-    GREEN: Write minimum implementation → confirm pass
-    REFACTOR: Clean up → confirm all tests still pass
-    │
-  ─────────────────────────────────
-  Next unit...
-  │
-  ▼
-After per-component units: regenerate shared types + contract tests
-  aidlc/tools/generate_shared.py
-  pytest aidlc/tests/contract/
-  aidlc/tools/contract_diff.py
-  │
-  ▼
-After contracts: cross-stack e2e against unified preview
-  pytest aidlc/tests/cross-stack/
-  │
-  ▼
-Gate: All layers green + contracts compatible + cross-stack pass
-```
-
-## Test Layers
-
-| Layer | When | Test Location | Run Against |
-|-------|------|---------------|-------------|
-| `unit` | Per function / module | `apps/{comp}/tests/unit/` | Local |
-| `integration` | Component + its DB / internal API | `apps/{comp}/tests/integration/` | Local container |
-| `e2e` | Whole component against preview | `apps/{comp}/tests/e2e/` | Component preview URL |
-| `cross-stack` | Full multi-client ↔ backend flow | `aidlc/tests/cross-stack/` | Unified stack preview URL |
-| `contract` | Contract shape + backward compat | `aidlc/tests/contract/` | Generated `aidlc/packages/shared/` |
-
-## TDD — Red
-
-Write one pytest test per assertion in the BDD scenario, at the layer the test plan specified.
-
-```python
-# apps/backend/tests/unit/test_auth.py
-def test_login_valid_credentials():
-    result = authenticate("user@example.com", "correct123")
-    assert result.token is not None
-    assert result.expires_in == 3600
-```
-
-```bash
-pytest apps/backend/tests/unit/test_auth.py -v
-# FAILED — authenticate() not defined  (RED ✓)
-```
-
-**Rule VRF-001:** Test must fail on first run.
-
-## TDD — Green
-
-Write the minimum code to make the test pass. No premature abstraction.
-
-```python
-# apps/backend/src/auth/login.py
-def authenticate(email, password):
-    if email == "user@example.com" and password == "correct123":
-        return AuthResult(token="jwt_token", expires_in=3600)
-    raise AuthError("Invalid credentials")
-```
-
-**Rule VRF-002:** Minimum code to pass.
-
-## TDD — Refactor
-
-```bash
-pytest --cov --cov-fail-under=80
-# All tests passed, coverage ≥80%  (REFACTOR ✓)
-```
-
-**Rule VRF-003:** Behavior must not change. All existing tests must pass before and after.
-
-## Contract Verification (INT-001, INT-002, INT-003)
-
-After per-component units pass and before cross-stack e2e:
-
-```bash
-# 1. Regenerate shared types from contracts
-aidlc/tools/generate_shared.py
-# → aidlc/packages/shared/{api,events} updated
-
-# 2. Run contract tests
-pytest aidlc/tests/contract/ --verbose
-# → All contract scenarios pass (uses packages/shared)
-
-# 3. Run contract compat check
-aidlc/tools/contract_diff.py --base main --head HEAD
-# → exit 0 = backward-compatible
-# → exit 1 = breaking change detected, BLOCKED unless human-approved
-```
-
-**Rule INT-001:** Contract tests must be 100% pass.
-
-**Rule INT-002:** Any breaking contract change (field removed, type changed, status code changed, required field added) is BLOCKED until a human approves the major version bump and a migration note is added to `aidlc/contracts/CHANGELOG.md`.
-
-**Rule INT-003:** Shared types must be generated, not hand-written. CI runs `generate_shared` and fails the build if `aidlc/packages/shared/` is out of date.
-
-## Cross-Stack E2E (STK-001)
-
-```bash
-export STACK_URL=$(deploy_stack --preview --output url)
-pytest aidlc/tests/cross-stack/ --stack-url $STACK_URL --verbose
-# All cross-stack scenarios pass
-```
-
-**Rule STK-001:** All `cross-stack` scenarios must pass. A single failure blocks delivery.
-
-## BDD Scenario Verification (per layer)
-
-```bash
-# Per component
-pytest-bdd apps/backend/features/ --verbose
-pytest-bdd apps/web/features/ --verbose       # e.g. via cucumber-js
-pytest-bdd apps/native/features/ --verbose    # or via detox/cavy
-pytest-bdd apps/desktop/features/ --verbose    # or via spectron
-pytest-bdd apps/wxa/features/ --verbose
-pytest-bdd apps/mya/features/ --verbose
-pytest-bdd apps/tta/features/ --verbose
-
-# Cross-stack
-pytest-bdd aidlc/features/cross-stack/ --verbose
-```
-
-## Quality Gates (Backpressure)
-
-All gates enforced on every attempt to mark a unit / change complete:
-
-```bash
-# Per component
-pytest apps/{component}/ --cov --cov-fail-under=80 && \
-  pytest-bdd apps/{component}/features/ --verbose && \
-  bandit -r apps/{component}/src/ -q && \
-  ! grep -rn "TODO\|FIXME\|HACK\|XXX" apps/{component}/src/
-
-# Cross-component
-pytest aidlc/tests/contract/ && \
-  aidlc/tools/contract_diff.py --base main --head HEAD
-
-# Stack
-pytest aidlc/tests/cross-stack/ --stack-url $STACK_URL
-```
-
-| Gate | Threshold | Rule | Scope |
-|------|-----------|------|-------|
-| Unit/integration coverage | ≥80% | VRF-005 | Per component |
-| BDD scenarios | 100% pass | VRF-004 | Per component |
-| Security | 0 vulns | VRF-005 | Per component |
-| No TODOs | 0 in src/ | VRF-005 | Per component |
-| Contract tests | 100% pass | INT-001 | Cross-component |
-| Contract compat | backward-compat | INT-002 | Cross-component |
-| Shared types | generated, in sync | INT-003 | Cross-component |
-| Cross-stack e2e | 100% pass | STK-001 | Stack |
-
-## Artifacts
-
-| Artifact | Location |
-|----------|----------|
-| TDD tests (unit/integration) | `apps/{comp}/tests/{unit,integration}/test_{feature}.py` |
-| TDD tests (e2e) | `apps/{comp}/tests/e2e/test_{feature}.py` |
-| BDD step defs (component) | `apps/{comp}/features/steps/test_{feature}_steps.py` |
-| BDD step defs (cross-stack) | `aidlc/features/cross-stack/steps/test_{feature}_steps.py` |
-| Implementation | `apps/{comp}/src/{module}/{feature}.py` |
-| Contract tests | `aidlc/tests/contract/test_{contract}.py` |
-| Cross-stack e2e | `aidlc/tests/cross-stack/test_{flow}.py` |
-| Contract diff | `aidlc/openspec/changes/{id}/contract-diff.md` (filled) |
-
-## Gate
-
-**Before advancing to Deliver phase:**
-- [ ] Per-component: All BDD scenarios pass (100%), coverage ≥80%, 0 vulns, no TODO
-- [ ] Contracts: `aidlc/tools/contract_diff.py` exits 0; `aidlc/tests/contract/` 100% pass; `aidlc/packages/shared/` regenerated and in sync
-- [ ] Cross-stack: `aidlc/tests/cross-stack/` 100% pass against stack preview
-- [ ] `aidlc/openspec/changes/{id}/contract-diff.md` is filled and reviewed
-- [ ] All existing tests still pass

package/ai-dlc-skill/phases/verify/prompt.md

@@ -1,43 +0,0 @@
-# Verify Phase Agent Prompt
-
-你是一个 AI-DLC Verify Phase Agent。
-由 Master Agent 委派处理测试验证。
-
-## 输入
-- `aidlc/openspec/changes/{id}/design.md` 和 `task-list.md`
-- BDD feature 文件
-
-## 任务
-
-1. **TDD Red-Green-Refactor**（按 DAG 顺序）
-   - 对每个 unit 的每个 BDD scenario：
-     - RED: 写 test → 确认失败
-     - GREEN: 写最小实现 → 确认通过
-     - REFACTOR: 重构清理 → 全部通过
-   - 测试按 layer 分类：unit / integration / e2e
-
-2. **Contract Verification**
-   - 重新生成 `aidlc/packages/shared/` 类型
-   - 运行 `pytest aidlc/tests/contract/`
-   - 运行 `aidlc/tools/contract_diff.py`
-
-3. **Cross-Stack e2e**
-   - 对 unified preview 运行 `aidlc/tests/cross-stack/`
-
-4. **Quality Gates**
-   - coverage ≥ 80%
-   - BDD scenarios 100% pass
-   - 0 vulns, no TODO
-
-## 输出产物
-- `apps/{component}/tests/{unit,integration,e2e}/test_{feature}.py`
-- `apps/{component}/features/steps/test_{feature}_steps.py`
-- `apps/{component}/src/{module}/{feature}.py`
-- `aidlc/tests/contract/test_{contract}.py`
-- `aidlc/tests/cross-stack/test_{flow}.py`
-- `aidlc/openspec/changes/{id}/contract-diff.md`（填充）
-
-## 约束
-- 遵守 `rules.md` 中的 VRF-001 到 VRF-006
-- 遵守 INT-001 到 INT-006
-- 遵守 STK-001 到 STK-006

package/ai-dlc-skill/phases/verify/rules.md

@@ -1,73 +0,0 @@
-# Verify Rules (VRF-*) + Integration Rules (INT-*)
-
-## VRF-001: TDD Red Phase
-**Severity:** MUST
-**Description:** Before writing implementation, write a test that asserts expected behavior. The test MUST fail on first run.
-**Valid:** `pytest apps/backend/tests/unit/test_auth.py -k test_login` → FAILED.
-**Invalid:** Test passes on first run.
-
-## VRF-002: TDD Green Phase
-**Severity:** MUST
-**Description:** Write the minimum code needed to make the test pass. No premature abstraction.
-**Valid:** Only the code path required by the test is implemented.
-**Invalid:** Adding database, caching, or logging before the test requires it.
-
-## VRF-003: TDD Refactor Phase
-**Severity:** MUST
-**Description:** After tests pass, refactor to improve code quality while keeping ALL tests green.
-**Valid:** `pytest --cov --cov-fail-under=80` → all pass.
-**Invalid:** Behavior change during refactoring.
-
-## VRF-004: BDD Scenario Pass Gate
-**Severity:** MUST
-**Description:** ALL BDD scenarios MUST pass at every required layer before marking complete.
-**Valid:** `pytest-bdd apps/{component}/features/ --verbose` → all pass.
-**Invalid:** Any failing BDD scenario.
-
-## VRF-005: Quality Gate Backpressure
-**Severity:** MUST
-**Description:** On every unit completion, ALL gates must pass: coverage ≥80%, BDD 100%, 0 vulns, no TODO.
-**Valid:** `pytest --cov --cov-fail-under=80 && bandit -r src/ -q && ! grep -rn "TODO" src/`
-**Invalid:** Any single gate fails.
-
-## VRF-006: Test Layer Correctness
-**Severity:** MUST
-**Description:** Each BDD scenario MUST be tested at the layer the plan specified. Cross-stack ≠ unit.
-**Valid:** Cross-stack scenarios in `aidlc/tests/cross-stack/` against STACK_URL.
-**Invalid:** Cross-stack scenario implemented as mocked unit test.
-
-## INT-001: Contract as Source of Truth
-**Severity:** MUST
-**Description:** All cross-component APIs and events MUST be defined in `contracts/` (OpenAPI/AsyncAPI/GraphQL) and tagged with `INT-FR-*`.
-**Valid:** `aidlc/contracts/api/auth.yaml` defines POST /auth/login; components use generated types.
-**Invalid:** Duplicate hand-written types across components with no contract file.
-
-## INT-002: Backward-Compatibility by Default
-**Severity:** MUST
-**Description:** Contract changes MUST be backward-compatible. Breaking = field removed, type changed, status code changed, required field added. BLOCKED until human approves MAJOR bump + CHANGELOG entry.
-**Valid:** Adding a new optional field (MINOR).
-**Invalid:** Removing a field without human approval.
-
-## INT-003: Generated Shared Types
-**Severity:** MUST
-**Description:** `aidlc/packages/shared/` generated from `aidlc/contracts/`. Component code MUST import from shared.
-**Valid:** `git diff --exit-code aidlc/packages/shared/` → clean after generation.
-**Invalid:** Hand-edited files under `aidlc/packages/shared/`.
-
-## INT-004: Contract Tests at INT FR Level
-**Severity:** MUST
-**Description:** Every `INT-FR-*` MUST have contract tests in `aidlc/tests/contract/` verifying schema.
-**Valid:** Provider-agnostic contract tests using generated shared types.
-**Invalid:** Contract tests calling real production backend.
-
-## INT-005: Cross-Stack Feature Coverage
-**Severity:** MUST
-**Description:** Every `INT-FR-*` MUST have ≥3 scenarios in `aidlc/features/cross-stack/` implemented in `aidlc/tests/cross-stack/`.
-**Valid:** Cross-stack scenarios running against unified STACK_URL.
-**Invalid:** INT-FR without cross-stack feature file.
-
-## INT-006: Contract Diff Artifact
-**Severity:** MUST
-**Description:** Every contract change MUST produce `aidlc/openspec/changes/{id}/contract-diff.md`.
-**Valid:** Generated by `aidlc/tools/contract_diff.py` with added/removed/changed fields.
-**Invalid:** Contract change merged without contract-diff.md.

package/ai-dlc-skill/practices/bdd.md

@@ -1,91 +0,0 @@
-# Behavior-Driven Development (BDD)
-
-BDD is the behavior specification and verification methodology used in Understand and Verify phases.
-
-## Role in AI-DLC
-
-| Phase | BDD Usage |
-|-------|-----------|
-| Understand | Feature files with Given/When/Then scenarios |
-| Verify | pytest-bdd scenario verification against implementation |
-| Deliver | BDD e2e tests against preview URL |
-
-## Gherkin Syntax
-
-| Keyword | Purpose |
-|---------|---------|
-| `Feature` | High-level feature description |
-| `Scenario` | Single behavior example |
-| `Given` | Precondition / starting state |
-| `When` | Action performed |
-| `Then` | Expected outcome |
-| `And` / `But` | Additional clause |
-| `Background` | Steps before every scenario |
-| `Scenario Outline` | Template with Examples table |
-| `@tag` | Metadata (FR ID, type) |
-
-## Scenario Coverage Rules
-
-Each FR must have at least 3 scenarios:
-
-| Type | Purpose | Example Tag |
-|------|---------|-------------|
-| Positive | Happy path, should work | `@FR-001 @positive` |
-| Negative | Error handling, should fail | `@FR-001 @negative` |
-| Edge case | Boundary conditions | `@FR-001 @edge` |
-
-## Example
-
-```gherkin
-@FR-001
-Feature: User Login
-
-  @FR-001 @positive
-  Scenario: Successful login
-    Given the user is on the login page
-    When the user submits email "user@test.com" and password "correct123"
-    Then the user receives a JWT token
-    And the user is redirected to dashboard
-
-  @FR-001 @negative
-  Scenario: Login with wrong password
-    Given the user is on the login page
-    When the user submits email "user@test.com" and password "wrong"
-    Then the user sees error "Invalid credentials"
-
-  @FR-001 @edge
-  Scenario: Login with empty fields
-    Given the user is on the login page
-    When the user submits email "" and password ""
-    Then the user sees error "Email and password are required"
-```
-
-## pytest-bdd Integration
-
-```python
-# features/steps/test_login_steps.py
-from pytest_bdd import scenarios, given, when, then, parsers
-
-scenarios("../auth/login.feature")
-
-@given("the user is on the login page")
-def login_page():
-    return LoginPage()
-
-@when(parsers.parse("the user submits email {email} and password {password}"))
-def submit(email, password):
-    ...
-```
-
-## Verification
-
-```bash
-# Run all BDD scenarios
-pytest-bdd features/ --verbose
-
-# Run scenarios for a specific FR
-pytest-bdd features/ -k "FR-001"
-
-# BDD scenario coverage
-pytest-bdd features/ --coverage
-```