@sun-asterisk/sungen 2.6.6 → 2.6.7

package/dist/cli/index.js

@@ -20,7 +20,7 @@ async function main() {
     program
         .name('sungen')
         .description('Deterministic E2E Test Compiler — Gherkin + Selectors → Playwright')
-        .version('2.6.6');
+        .version('2.6.7');
     // Global options
     program
         .option('-v, --verbose', 'Enable verbose logging');

package/dist/orchestrator/templates/ai-instructions/claude-cmd-create-test.md

@@ -27,7 +27,11 @@ Parse **name** from `$ARGUMENTS`. If missing, ask the user.
 
 1. **Flow**: Verify `qa/flows/<name>/` exists. If not → `/sungen:add-flow` first.
    **Screen**: Verify `qa/screens/<name>/` exists. If not → `/sungen:add-screen` first.
-2. Check if `.feature` file already has scenarios. If yes → use `AskUserQuestion` to ask the update mode (see `sungen-tc-generation` skill for details). If no → fresh creation.
+2. Check if `.feature` file already has scenarios.
+   - If yes → use `AskUserQuestion` to ask the update mode (see `sungen-tc-generation` skill — mode depends on which tiers already exist).
+   - If no → fresh creation. Use `AskUserQuestion` to ask generation scope:
+     - **Tier 1 — Critical & High priority** — ~10-15 scenarios/section covering happy paths, core validation, security basics **(Recommended)**
+     - **Full coverage — All tiers at once** — generates Tier 1 + 2 + 3 in one run. Large output (~40-60 scenarios/section), best for experienced users who want complete coverage immediately
 3. **Read requirements & resolve visual source** — check `qa/<screens|flows>/<name>/requirements/`:
    - If `spec.md` exists → read it as PRIMARY source (sections, fields, validation rules, business rules, states).
    - If `test-viewpoint.md` exists → read it. If it only contains HTML comments (scaffold template), use `AskUserQuestion` to ask:
@@ -49,11 +53,23 @@ Parse **name** from `$ARGUMENTS`. If missing, ask the user.
 
 4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy.
 5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **For flows**: use `[Screen:Element]` namespace format, namespace test-data by phase, add `@flow` tag.
-6. Show summary, then use `AskUserQuestion` to offer next steps:
-
-- **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
-- **`/sungen:run-test <name>`** — Skip review, generate selectors and run tests now
-- **`/sungen:create-test <name>`** — Expand coverage: add @normal + @low scenarios
-- **Done for now** — I'll come back later
+6. Show summary, then use `AskUserQuestion` to offer next steps based on which tier was just generated:
+
+   **After Tier 1 generation:**
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen:run-test <name>`** — Skip review, generate selectors and run tests now
+   - **`/sungen:create-test <name>`** — Expand coverage: add @normal + @low scenarios (Tier 2)
+   - **Done for now** — I'll come back later
+
+   **After Tier 2 generation:**
+   - **`/sungen:create-test <name>`** — Deep coverage: add BVA combos, cross-field validation, negative inputs, race conditions (Tier 3) (Recommended)
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
+
+   **After Tier 3 or Full generation:**
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen:run-test`.

package/dist/orchestrator/templates/ai-instructions/claude-skill-tc-generation.md

@@ -14,18 +14,38 @@ Generate **focused test cases per screen section** using a **tier-based approach
 |---|---|---|---|
 | **Tier 1** (default) | `@high` | Happy paths, required validation, core business rules, security basics | First run of `create-test` |
 | **Tier 2** (expand) | `@normal` + `@low` | UI presence, optional validation, edge cases, cosmetic checks | User runs `create-test` again with "Add viewpoints" mode |
+| **Tier 3** (deep) | `@high` + `@normal` | Extra BVA combinations, cross-field validation, negative/destructive inputs, concurrent/race conditions, complex state transitions | Recommended after Tier 2 completes |
+| **Full** (all-at-once) | All | Tier 1 + 2 + 3 combined in one run | Option at first run, **not recommended** — large output |
 
-**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior.
+**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior. A **Full** option is available but not recommended — it generates all tiers at once, producing very large output (~40-60 scenarios/section).
 
-**Round 2 (Tier 2)** expands to full coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+**Round 2 (Tier 2)** expands coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+
+**Round 3 (Tier 3)** deepens coverage with advanced test design techniques after Tier 2 is complete. This tier focuses on scenarios that Tier 1+2 didn't cover:
+- **Extra BVA combinations**: additional boundary points not covered in Tier 1 (e.g., `min+1`, `max-1`, typical values between boundaries)
+- **Cross-field validation**: field A value affects field B behavior (dependent fields, conditional required, cascading dropdowns)
+- **Negative/destructive inputs**: SQL injection, XSS payloads, special characters, excessively long strings, unicode edge cases
+- **Concurrent/race conditions**: double submit, back button after submit, multiple tabs, session expiry mid-action
+- **Complex state transitions**: multi-step state changes, undo/redo, conflicting state updates, transition from every non-obvious state
 
 ## Update Mode
 
-When `.feature` already has scenarios, summarize and ask:
+When `.feature` already has scenarios, summarize existing coverage and ask:
+
+**If only Tier 1 exists** (only `@high` scenarios):
 1. **Add new sections** — append new sections with Tier 2 (`@normal` + `@low`) scenarios, continue numbering
 2. **Add viewpoints** — expand existing sections with Tier 2 (`@normal` + `@low`) scenarios
 3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
 
+**If Tier 1 + 2 exist** (`@high` + `@normal` + `@low` scenarios):
+1. **Deep coverage (Tier 3)** — add advanced scenarios: extra BVA, cross-field validation, negative inputs, race conditions **(Recommended)**
+2. **Add new sections** — append new sections with Tier 2 scenarios, continue numbering
+3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
+**If Tier 1 + 2 + 3 exist** (full coverage already):
+1. **Add new sections** — append new sections if screen has changed
+2. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
 For append: read highest `VP-<CAT>-<NNN>`, continue from next number. Never modify existing scenarios.
 
 ## Requirements-Driven Generation
@@ -91,6 +111,13 @@ Use `sungen-viewpoint` skill for per-pattern checklists across 4 viewpoints: UI/
 **Tier-aware gap filling:**
 - **Tier 1 (first run)**: only add `@high` items from the checklists — core security checks (VP-SEC), required field validation (VP-VAL), key state transitions (VP-LOGIC). Skip `@normal`/`@low` items like hover states, empty states, tooltips.
 - **Tier 2 (expand run)**: add `@normal` + `@low` scenarios — UI presence, optional validation, edge cases, cosmetic checks, keyboard nav, hover effects.
+- **Tier 3 (deep run)**: do NOT use viewpoint checklists. Instead, re-apply test design techniques with deeper analysis:
+  - **BVA**: expand from 4-point to 6-point (`min-1`, `min`, `min+1`, `max-1`, `max`, `max+1`) + typical mid-range value
+  - **Decision Table**: enumerate combinations previously capped — cover remaining outcome rows
+  - **Cross-field**: identify field dependencies from spec, generate one scenario per dependency
+  - **Negative inputs**: add security-oriented inputs (SQL `' OR 1=1`, XSS `<script>`, special chars `<>&"'`, max+100 length)
+  - **Race conditions**: double-click submit, browser back after POST, concurrent edit by two users
+- **Full (all-at-once)**: apply Tier 1 + 2 + 3 rules in a single generation pass. Use all techniques at maximum depth.
 
 **Validation rule**: capture actual error messages from live page or spec.md. Use `User see {{error_var}}` — never assert just "is visible".
 
@@ -242,6 +269,8 @@ Feature: <Screen> Screen
 
 **Tier 2 (expand run)** adds `@normal` + `@low` scenarios like UI field presence, hover states, tooltips, empty states.
 
+**Tier 3 (deep run)** adds advanced `@high` + `@normal` scenarios: extra BVA boundaries, cross-field validation, negative/destructive inputs, concurrent/race conditions.
+
 ### When to use DataTable vs Row Scope
 
 | Pattern | Use when |

package/dist/orchestrator/templates/ai-instructions/copilot-cmd-create-test.md

@@ -22,7 +22,11 @@ You are a **Senior QA Engineer**. You structure test cases by viewpoint categori
 
 1. **Flow**: Verify `qa/flows/${input:name}/` exists. If not → `/sungen-add-flow` first.
    **Screen**: Verify `qa/screens/${input:name}/` exists. If not → `/sungen-add-screen` first.
-2. Check if `.feature` already has scenarios. If yes → summarize existing coverage and ask: **1) Add new sections**, **2) Add viewpoints to existing sections**, or **3) Replace all**. See `sungen-tc-generation` skill for update mode details.
+2. Check if `.feature` already has scenarios.
+   - If yes → summarize existing coverage and ask update mode (options depend on which tiers already exist — see `sungen-tc-generation` skill for details).
+   - If no → fresh creation. Ask generation scope:
+     - **1) Tier 1 — Critical & High priority** — ~10-15 scenarios/section covering happy paths, core validation, security basics **(Recommended)**
+     - **2) Full coverage — All tiers at once** — generates Tier 1 + 2 + 3 in one run. Large output (~40-60 scenarios/section), best for experienced users who want complete coverage immediately
 3. **Read requirements & resolve visual source** — check `<base>/${input:name}/requirements/`:
    - If `spec.md` exists → read it as PRIMARY source (sections, fields, validation rules, business rules, states).
    - If `test-viewpoint.md` exists → read it. If it only contains HTML comments (scaffold template), ask:
@@ -44,11 +48,23 @@ You are a **Senior QA Engineer**. You structure test cases by viewpoint categori
 
 4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy. Present sections as a numbered list and let user pick.
 5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **For flows**: use `[Screen:Element]` namespace format, namespace test-data by phase, add `@flow` tag.
-6. Show summary and offer next steps:
+6. Show summary and offer next steps based on which tier was just generated:
 
-- **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
-- **`/sungen-run-test ${input:name}`** — Skip review, generate selectors and run tests now
-- **`/sungen-create-test ${input:name}`** — Expand coverage: add @normal + @low scenarios
-- **Done for now** — I'll come back later
+   **After Tier 1 generation:**
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen-run-test ${input:name}`** — Skip review, generate selectors and run tests now
+   - **`/sungen-create-test ${input:name}`** — Expand coverage: add @normal + @low scenarios (Tier 2)
+   - **Done for now** — I'll come back later
+
+   **After Tier 2 generation:**
+   - **`/sungen-create-test ${input:name}`** — Deep coverage: add BVA combos, cross-field validation, negative inputs, race conditions (Tier 3) (Recommended)
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality
+   - **`/sungen-run-test ${input:name}`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
+
+   **After Tier 3 or Full generation:**
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen-run-test ${input:name}`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen-run-test`.

package/dist/orchestrator/templates/ai-instructions/github-skill-sungen-tc-generation.md

@@ -14,18 +14,38 @@ Generate **focused test cases per screen section** using a **tier-based approach
 |---|---|---|---|
 | **Tier 1** (default) | `@high` | Happy paths, required validation, core business rules, security basics | First run of `create-test` |
 | **Tier 2** (expand) | `@normal` + `@low` | UI presence, optional validation, edge cases, cosmetic checks | User runs `create-test` again with "Add viewpoints" mode |
+| **Tier 3** (deep) | `@high` + `@normal` | Extra BVA combinations, cross-field validation, negative/destructive inputs, concurrent/race conditions, complex state transitions | Recommended after Tier 2 completes |
+| **Full** (all-at-once) | All | Tier 1 + 2 + 3 combined in one run | Option at first run, **not recommended** — large output |
 
-**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior.
+**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior. A **Full** option is available but not recommended — it generates all tiers at once, producing very large output (~40-60 scenarios/section).
 
-**Round 2 (Tier 2)** expands to full coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+**Round 2 (Tier 2)** expands coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+
+**Round 3 (Tier 3)** deepens coverage with advanced test design techniques after Tier 2 is complete. This tier focuses on scenarios that Tier 1+2 didn't cover:
+- **Extra BVA combinations**: additional boundary points not covered in Tier 1 (e.g., `min+1`, `max-1`, typical values between boundaries)
+- **Cross-field validation**: field A value affects field B behavior (dependent fields, conditional required, cascading dropdowns)
+- **Negative/destructive inputs**: SQL injection, XSS payloads, special characters, excessively long strings, unicode edge cases
+- **Concurrent/race conditions**: double submit, back button after submit, multiple tabs, session expiry mid-action
+- **Complex state transitions**: multi-step state changes, undo/redo, conflicting state updates, transition from every non-obvious state
 
 ## Update Mode
 
-When `.feature` already has scenarios, summarize and ask:
+When `.feature` already has scenarios, summarize existing coverage and ask:
+
+**If only Tier 1 exists** (only `@high` scenarios):
 1. **Add new sections** — append new sections with Tier 2 (`@normal` + `@low`) scenarios, continue numbering
 2. **Add viewpoints** — expand existing sections with Tier 2 (`@normal` + `@low`) scenarios
 3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
 
+**If Tier 1 + 2 exist** (`@high` + `@normal` + `@low` scenarios):
+1. **Deep coverage (Tier 3)** — add advanced scenarios: extra BVA, cross-field validation, negative inputs, race conditions **(Recommended)**
+2. **Add new sections** — append new sections with Tier 2 scenarios, continue numbering
+3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
+**If Tier 1 + 2 + 3 exist** (full coverage already):
+1. **Add new sections** — append new sections if screen has changed
+2. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
 For append: read highest `VP-<CAT>-<NNN>`, continue from next number. Never modify existing scenarios.
 
 ## Requirements-Driven Generation
@@ -104,6 +124,13 @@ Use `sungen-viewpoint` skill for per-pattern checklists across 4 viewpoints: UI/
 **Tier-aware gap filling:**
 - **Tier 1 (first run)**: only add `@high` items from the checklists — core security checks (VP-SEC), required field validation (VP-VAL), key state transitions (VP-LOGIC). Skip `@normal`/`@low` items like hover states, empty states, tooltips.
 - **Tier 2 (expand run)**: add `@normal` + `@low` scenarios — UI presence, optional validation, edge cases, cosmetic checks, keyboard nav, hover effects.
+- **Tier 3 (deep run)**: do NOT use viewpoint checklists. Instead, re-apply test design techniques with deeper analysis:
+  - **BVA**: expand from 4-point to 6-point (`min-1`, `min`, `min+1`, `max-1`, `max`, `max+1`) + typical mid-range value
+  - **Decision Table**: enumerate combinations previously capped — cover remaining outcome rows
+  - **Cross-field**: identify field dependencies from spec, generate one scenario per dependency
+  - **Negative inputs**: add security-oriented inputs (SQL `' OR 1=1`, XSS `<script>`, special chars `<>&"'`, max+100 length)
+  - **Race conditions**: double-click submit, browser back after POST, concurrent edit by two users
+- **Full (all-at-once)**: apply Tier 1 + 2 + 3 rules in a single generation pass. Use all techniques at maximum depth.
 
 **Validation rule**: capture actual error messages from live page or spec.md. Use `User see {{error_var}}` — never assert just "is visible".
 
@@ -255,6 +282,8 @@ Feature: <Screen> Screen
 
 **Tier 2 (expand run)** adds `@normal` + `@low` scenarios like UI field presence, hover states, tooltips, empty states.
 
+**Tier 3 (deep run)** adds advanced `@high` + `@normal` scenarios: extra BVA boundaries, cross-field validation, negative/destructive inputs, concurrent/race conditions.
+
 ### When to use DataTable vs Row Scope
 
 | Pattern | Use when |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sun-asterisk/sungen",
-  "version": "2.6.6",
+  "version": "2.6.7",
   "description": "Deterministic E2E Test Compiler - Gherkin + Selectors → Playwright tests",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/src/cli/index.ts

@@ -21,7 +21,7 @@ async function main() {
   program
     .name('sungen')
     .description('Deterministic E2E Test Compiler — Gherkin + Selectors → Playwright')
-    .version('2.6.6');
+    .version('2.6.7');
 
   // Global options
   program

package/src/orchestrator/templates/ai-instructions/claude-cmd-create-test.md

@@ -27,7 +27,11 @@ Parse **name** from `$ARGUMENTS`. If missing, ask the user.
 
 1. **Flow**: Verify `qa/flows/<name>/` exists. If not → `/sungen:add-flow` first.
    **Screen**: Verify `qa/screens/<name>/` exists. If not → `/sungen:add-screen` first.
-2. Check if `.feature` file already has scenarios. If yes → use `AskUserQuestion` to ask the update mode (see `sungen-tc-generation` skill for details). If no → fresh creation.
+2. Check if `.feature` file already has scenarios.
+   - If yes → use `AskUserQuestion` to ask the update mode (see `sungen-tc-generation` skill — mode depends on which tiers already exist).
+   - If no → fresh creation. Use `AskUserQuestion` to ask generation scope:
+     - **Tier 1 — Critical & High priority** — ~10-15 scenarios/section covering happy paths, core validation, security basics **(Recommended)**
+     - **Full coverage — All tiers at once** — generates Tier 1 + 2 + 3 in one run. Large output (~40-60 scenarios/section), best for experienced users who want complete coverage immediately
 3. **Read requirements & resolve visual source** — check `qa/<screens|flows>/<name>/requirements/`:
    - If `spec.md` exists → read it as PRIMARY source (sections, fields, validation rules, business rules, states).
    - If `test-viewpoint.md` exists → read it. If it only contains HTML comments (scaffold template), use `AskUserQuestion` to ask:
@@ -49,11 +53,23 @@ Parse **name** from `$ARGUMENTS`. If missing, ask the user.
 
 4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy.
 5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **For flows**: use `[Screen:Element]` namespace format, namespace test-data by phase, add `@flow` tag.
-6. Show summary, then use `AskUserQuestion` to offer next steps:
-
-- **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
-- **`/sungen:run-test <name>`** — Skip review, generate selectors and run tests now
-- **`/sungen:create-test <name>`** — Expand coverage: add @normal + @low scenarios
-- **Done for now** — I'll come back later
+6. Show summary, then use `AskUserQuestion` to offer next steps based on which tier was just generated:
+
+   **After Tier 1 generation:**
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen:run-test <name>`** — Skip review, generate selectors and run tests now
+   - **`/sungen:create-test <name>`** — Expand coverage: add @normal + @low scenarios (Tier 2)
+   - **Done for now** — I'll come back later
+
+   **After Tier 2 generation:**
+   - **`/sungen:create-test <name>`** — Deep coverage: add BVA combos, cross-field validation, negative inputs, race conditions (Tier 3) (Recommended)
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
+
+   **After Tier 3 or Full generation:**
+   - **`/sungen:review <name>`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen:run-test <name>`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen:run-test`.

package/src/orchestrator/templates/ai-instructions/claude-skill-tc-generation.md

@@ -14,18 +14,38 @@ Generate **focused test cases per screen section** using a **tier-based approach
 |---|---|---|---|
 | **Tier 1** (default) | `@high` | Happy paths, required validation, core business rules, security basics | First run of `create-test` |
 | **Tier 2** (expand) | `@normal` + `@low` | UI presence, optional validation, edge cases, cosmetic checks | User runs `create-test` again with "Add viewpoints" mode |
+| **Tier 3** (deep) | `@high` + `@normal` | Extra BVA combinations, cross-field validation, negative/destructive inputs, concurrent/race conditions, complex state transitions | Recommended after Tier 2 completes |
+| **Full** (all-at-once) | All | Tier 1 + 2 + 3 combined in one run | Option at first run, **not recommended** — large output |
 
-**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior.
+**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior. A **Full** option is available but not recommended — it generates all tiers at once, producing very large output (~40-60 scenarios/section).
 
-**Round 2 (Tier 2)** expands to full coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+**Round 2 (Tier 2)** expands coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+
+**Round 3 (Tier 3)** deepens coverage with advanced test design techniques after Tier 2 is complete. This tier focuses on scenarios that Tier 1+2 didn't cover:
+- **Extra BVA combinations**: additional boundary points not covered in Tier 1 (e.g., `min+1`, `max-1`, typical values between boundaries)
+- **Cross-field validation**: field A value affects field B behavior (dependent fields, conditional required, cascading dropdowns)
+- **Negative/destructive inputs**: SQL injection, XSS payloads, special characters, excessively long strings, unicode edge cases
+- **Concurrent/race conditions**: double submit, back button after submit, multiple tabs, session expiry mid-action
+- **Complex state transitions**: multi-step state changes, undo/redo, conflicting state updates, transition from every non-obvious state
 
 ## Update Mode
 
-When `.feature` already has scenarios, summarize and ask:
+When `.feature` already has scenarios, summarize existing coverage and ask:
+
+**If only Tier 1 exists** (only `@high` scenarios):
 1. **Add new sections** — append new sections with Tier 2 (`@normal` + `@low`) scenarios, continue numbering
 2. **Add viewpoints** — expand existing sections with Tier 2 (`@normal` + `@low`) scenarios
 3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
 
+**If Tier 1 + 2 exist** (`@high` + `@normal` + `@low` scenarios):
+1. **Deep coverage (Tier 3)** — add advanced scenarios: extra BVA, cross-field validation, negative inputs, race conditions **(Recommended)**
+2. **Add new sections** — append new sections with Tier 2 scenarios, continue numbering
+3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
+**If Tier 1 + 2 + 3 exist** (full coverage already):
+1. **Add new sections** — append new sections if screen has changed
+2. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
 For append: read highest `VP-<CAT>-<NNN>`, continue from next number. Never modify existing scenarios.
 
 ## Requirements-Driven Generation
@@ -91,6 +111,13 @@ Use `sungen-viewpoint` skill for per-pattern checklists across 4 viewpoints: UI/
 **Tier-aware gap filling:**
 - **Tier 1 (first run)**: only add `@high` items from the checklists — core security checks (VP-SEC), required field validation (VP-VAL), key state transitions (VP-LOGIC). Skip `@normal`/`@low` items like hover states, empty states, tooltips.
 - **Tier 2 (expand run)**: add `@normal` + `@low` scenarios — UI presence, optional validation, edge cases, cosmetic checks, keyboard nav, hover effects.
+- **Tier 3 (deep run)**: do NOT use viewpoint checklists. Instead, re-apply test design techniques with deeper analysis:
+  - **BVA**: expand from 4-point to 6-point (`min-1`, `min`, `min+1`, `max-1`, `max`, `max+1`) + typical mid-range value
+  - **Decision Table**: enumerate combinations previously capped — cover remaining outcome rows
+  - **Cross-field**: identify field dependencies from spec, generate one scenario per dependency
+  - **Negative inputs**: add security-oriented inputs (SQL `' OR 1=1`, XSS `<script>`, special chars `<>&"'`, max+100 length)
+  - **Race conditions**: double-click submit, browser back after POST, concurrent edit by two users
+- **Full (all-at-once)**: apply Tier 1 + 2 + 3 rules in a single generation pass. Use all techniques at maximum depth.
 
 **Validation rule**: capture actual error messages from live page or spec.md. Use `User see {{error_var}}` — never assert just "is visible".
 
@@ -242,6 +269,8 @@ Feature: <Screen> Screen
 
 **Tier 2 (expand run)** adds `@normal` + `@low` scenarios like UI field presence, hover states, tooltips, empty states.
 
+**Tier 3 (deep run)** adds advanced `@high` + `@normal` scenarios: extra BVA boundaries, cross-field validation, negative/destructive inputs, concurrent/race conditions.
+
 ### When to use DataTable vs Row Scope
 
 | Pattern | Use when |

package/src/orchestrator/templates/ai-instructions/copilot-cmd-create-test.md

@@ -22,7 +22,11 @@ You are a **Senior QA Engineer**. You structure test cases by viewpoint categori
 
 1. **Flow**: Verify `qa/flows/${input:name}/` exists. If not → `/sungen-add-flow` first.
    **Screen**: Verify `qa/screens/${input:name}/` exists. If not → `/sungen-add-screen` first.
-2. Check if `.feature` already has scenarios. If yes → summarize existing coverage and ask: **1) Add new sections**, **2) Add viewpoints to existing sections**, or **3) Replace all**. See `sungen-tc-generation` skill for update mode details.
+2. Check if `.feature` already has scenarios.
+   - If yes → summarize existing coverage and ask update mode (options depend on which tiers already exist — see `sungen-tc-generation` skill for details).
+   - If no → fresh creation. Ask generation scope:
+     - **1) Tier 1 — Critical & High priority** — ~10-15 scenarios/section covering happy paths, core validation, security basics **(Recommended)**
+     - **2) Full coverage — All tiers at once** — generates Tier 1 + 2 + 3 in one run. Large output (~40-60 scenarios/section), best for experienced users who want complete coverage immediately
 3. **Read requirements & resolve visual source** — check `<base>/${input:name}/requirements/`:
    - If `spec.md` exists → read it as PRIMARY source (sections, fields, validation rules, business rules, states).
    - If `test-viewpoint.md` exists → read it. If it only contains HTML comments (scaffold template), ask:
@@ -44,11 +48,23 @@ You are a **Senior QA Engineer**. You structure test cases by viewpoint categori
 
 4. Follow the `sungen-tc-generation` skill for section identification, viewpoint generation, and output format. **For flows**, use the "Flow Test Generation" section in the skill. When requirements exist, use the "Requirements-Driven Generation" strategy. Present sections as a numbered list and let user pick.
 5. Generate or update `.feature` + `test-data.yaml` following `sungen-gherkin-syntax` and `sungen-tc-generation` skills. **For flows**: use `[Screen:Element]` namespace format, namespace test-data by phase, add `@flow` tag.
-6. Show summary and offer next steps:
+6. Show summary and offer next steps based on which tier was just generated:
 
-- **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
-- **`/sungen-run-test ${input:name}`** — Skip review, generate selectors and run tests now
-- **`/sungen-create-test ${input:name}`** — Expand coverage: add @normal + @low scenarios
-- **Done for now** — I'll come back later
+   **After Tier 1 generation:**
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen-run-test ${input:name}`** — Skip review, generate selectors and run tests now
+   - **`/sungen-create-test ${input:name}`** — Expand coverage: add @normal + @low scenarios (Tier 2)
+   - **Done for now** — I'll come back later
+
+   **After Tier 2 generation:**
+   - **`/sungen-create-test ${input:name}`** — Deep coverage: add BVA combos, cross-field validation, negative inputs, race conditions (Tier 3) (Recommended)
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality
+   - **`/sungen-run-test ${input:name}`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
+
+   **After Tier 3 or Full generation:**
+   - **`/sungen-review ${input:name}`** — Review syntax, coverage, viewpoint quality (Recommended)
+   - **`/sungen-run-test ${input:name}`** — Generate selectors and run tests now
+   - **Done for now** — I'll come back later
 
 **No selectors.yaml** — selectors are generated during `/sungen-run-test`.

package/src/orchestrator/templates/ai-instructions/github-skill-sungen-tc-generation.md

@@ -14,18 +14,38 @@ Generate **focused test cases per screen section** using a **tier-based approach
 |---|---|---|---|
 | **Tier 1** (default) | `@high` | Happy paths, required validation, core business rules, security basics | First run of `create-test` |
 | **Tier 2** (expand) | `@normal` + `@low` | UI presence, optional validation, edge cases, cosmetic checks | User runs `create-test` again with "Add viewpoints" mode |
+| **Tier 3** (deep) | `@high` + `@normal` | Extra BVA combinations, cross-field validation, negative/destructive inputs, concurrent/race conditions, complex state transitions | Recommended after Tier 2 completes |
+| **Full** (all-at-once) | All | Tier 1 + 2 + 3 combined in one run | Option at first run, **not recommended** — large output |
 
-**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior.
+**Round 1 (Tier 1)** targets **~10-15 scenarios per section** — enough to cover critical flows and catch real bugs. This is the default behavior. A **Full** option is available but not recommended — it generates all tiers at once, producing very large output (~40-60 scenarios/section).
 
-**Round 2 (Tier 2)** expands to full coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+**Round 2 (Tier 2)** expands coverage when the user explicitly chooses "Add viewpoints" or "Add new sections" update mode. Only then generate `@normal` + `@low` scenarios to fill coverage gaps.
+
+**Round 3 (Tier 3)** deepens coverage with advanced test design techniques after Tier 2 is complete. This tier focuses on scenarios that Tier 1+2 didn't cover:
+- **Extra BVA combinations**: additional boundary points not covered in Tier 1 (e.g., `min+1`, `max-1`, typical values between boundaries)
+- **Cross-field validation**: field A value affects field B behavior (dependent fields, conditional required, cascading dropdowns)
+- **Negative/destructive inputs**: SQL injection, XSS payloads, special characters, excessively long strings, unicode edge cases
+- **Concurrent/race conditions**: double submit, back button after submit, multiple tabs, session expiry mid-action
+- **Complex state transitions**: multi-step state changes, undo/redo, conflicting state updates, transition from every non-obvious state
 
 ## Update Mode
 
-When `.feature` already has scenarios, summarize and ask:
+When `.feature` already has scenarios, summarize existing coverage and ask:
+
+**If only Tier 1 exists** (only `@high` scenarios):
 1. **Add new sections** — append new sections with Tier 2 (`@normal` + `@low`) scenarios, continue numbering
 2. **Add viewpoints** — expand existing sections with Tier 2 (`@normal` + `@low`) scenarios
 3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
 
+**If Tier 1 + 2 exist** (`@high` + `@normal` + `@low` scenarios):
+1. **Deep coverage (Tier 3)** — add advanced scenarios: extra BVA, cross-field validation, negative inputs, race conditions **(Recommended)**
+2. **Add new sections** — append new sections with Tier 2 scenarios, continue numbering
+3. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
+**If Tier 1 + 2 + 3 exist** (full coverage already):
+1. **Add new sections** — append new sections if screen has changed
+2. **Replace all** — overwrite with fresh Tier 1 (`@high`) generation
+
 For append: read highest `VP-<CAT>-<NNN>`, continue from next number. Never modify existing scenarios.
 
 ## Requirements-Driven Generation
@@ -104,6 +124,13 @@ Use `sungen-viewpoint` skill for per-pattern checklists across 4 viewpoints: UI/
 **Tier-aware gap filling:**
 - **Tier 1 (first run)**: only add `@high` items from the checklists — core security checks (VP-SEC), required field validation (VP-VAL), key state transitions (VP-LOGIC). Skip `@normal`/`@low` items like hover states, empty states, tooltips.
 - **Tier 2 (expand run)**: add `@normal` + `@low` scenarios — UI presence, optional validation, edge cases, cosmetic checks, keyboard nav, hover effects.
+- **Tier 3 (deep run)**: do NOT use viewpoint checklists. Instead, re-apply test design techniques with deeper analysis:
+  - **BVA**: expand from 4-point to 6-point (`min-1`, `min`, `min+1`, `max-1`, `max`, `max+1`) + typical mid-range value
+  - **Decision Table**: enumerate combinations previously capped — cover remaining outcome rows
+  - **Cross-field**: identify field dependencies from spec, generate one scenario per dependency
+  - **Negative inputs**: add security-oriented inputs (SQL `' OR 1=1`, XSS `<script>`, special chars `<>&"'`, max+100 length)
+  - **Race conditions**: double-click submit, browser back after POST, concurrent edit by two users
+- **Full (all-at-once)**: apply Tier 1 + 2 + 3 rules in a single generation pass. Use all techniques at maximum depth.
 
 **Validation rule**: capture actual error messages from live page or spec.md. Use `User see {{error_var}}` — never assert just "is visible".
 
@@ -255,6 +282,8 @@ Feature: <Screen> Screen
 
 **Tier 2 (expand run)** adds `@normal` + `@low` scenarios like UI field presence, hover states, tooltips, empty states.
 
+**Tier 3 (deep run)** adds advanced `@high` + `@normal` scenarios: extra BVA boundaries, cross-field validation, negative/destructive inputs, concurrent/race conditions.
+
 ### When to use DataTable vs Row Scope
 
 | Pattern | Use when |