@anhth2/spec-driven-dev-plugin 0.6.0 → 0.7.0

package/core/commands/run-tests.md

@@ -31,7 +31,7 @@ Display and wait for response:
 ```
 ⚙️  MODEL CHECK
 ──────────────────────────────────────────────────────────────────
-  Recommended  : claude-opus-4-5 (or claude-opus-4)
+  Recommended  : claude-opus-4 (or latest Opus model)
   Why needed   : Spec analysis, architecture review, code generation
                  require deep reasoning. Smaller models miss edge cases.
 
@@ -84,7 +84,7 @@ Wait for explicit "Y" or "N" from the user before continuing.
 - "N" → stop and ask what the user wants to change.
 
 
-*Note: For this command, the target in Step 1 is a UC-ID or service name from `$ARGUMENTS`. Context loading provides `conventions.test_command`.*
+*Note: For this command, the target in Step 1 is a UC-ID or service name. Context loading provides `conventions.test_command` and `tech_stack.module`.*
 
 ## Context
 # Context Loader — Load All Project Context
@@ -140,7 +140,7 @@ If `paths` section is absent, use these defaults:
 - `domain_knowledge_dir` = `specs/domain-knowledge`
 - `business_dictionary` = `specs/domain-knowledge/business-dictionary.md`
 - `core_entities` = `specs/domain-knowledge/core-entities.md`
-- `tech_docs_dir` = `tech-docs`
+- `tech_docs_dir` = `specs/tech-docs`
 - `trace_dir` = `.trace`
 
 If `tech_stack.module` is set, also load `.agent/modules/{module}/stack-profile.yaml` if it exists.
@@ -217,6 +217,26 @@ If the file does not exist → skip silently.
 
 ---
 
+## Step 6.5 — [PLATFORM] Derive active_module and platform_type
+
+Using `tech_stack.module` loaded in Step 1, derive and store two variables for use by all downstream commands:
+
+```
+active_module = tech_stack.module   (e.g. "java-spring", "react", "flutter")
+```
+
+| `platform_type` | Modules |
+|---|---|
+| `backend` | `java-spring`, `golang`, `dotnet`, `php-laravel`, `context-engineering` |
+| `web-frontend` | `react`, `nextjs`, `vue`, `nuxt`, `angular` |
+| `mobile` | `flutter`, `react-native`, `ios-swiftui`, `android-compose` |
+
+If `tech_stack.module` is blank or not recognized → set `platform_type = "unknown"` and flag as ⚠️ in the Step 7 recap.
+
+These two variables (`active_module`, `platform_type`) are the canonical source for all branching logic in commands that need platform-specific behavior (generate-tests, debug, fix-bug, smoke-test).
+
+---
+
 ## Step 7 — [RECAP] Working Memory Recap (anti-lost-in-middle)
 
 After loading all context, synthesize and output a compact summary block.
@@ -227,6 +247,7 @@ Output exactly this block:
 ```
 [CTX LOADED]
 Stack     : {language} / {framework} / {database}
+Platform  : {active_module} ({platform_type})
 Layers    : {layer order from CLAUDE.md §2, e.g., Controller → Facade → Service → Repository}
 Ticket    : {ticket_prefix}-
 Dict      : {loaded — N canonical terms, M banned terms | missing}
@@ -252,25 +273,142 @@ After completing all steps, you have loaded:
 Proceed to the next step of the calling command.
 
 
+---
+
+## Service Detection
+
+Read `active_module` from context (resolved in context-loader Step 1).
+Use it to select the correct run command and error analysis table below.
+
 ---
 
 ## Run
+
+### If `platform_type = backend`
+
 ```bash
-{conventions.test_command}                          # all tests in module
-{conventions.test_command} --class {ClassName}      # specific class (faster)
-{conventions.test_command} --pattern "*{Resource}*" # by pattern
+# Run all tests for this UC
+{conventions.test_command}
+
+# Scoped to specific class (faster feedback)
+# java-spring:
+mvn test -Dtest={ClassName}
+# golang:
+go test ./... -run Test{FunctionName}
+# dotnet:
+dotnet test --filter "FullyQualifiedName~{ClassName}"
+# php-laravel:
+php artisan test --filter {ClassName}
+# context-engineering (pytest):
+pytest tests/{domain}/{test_file}.py -v
+pytest tests/{domain}/{test_file}.py::{TestClass}::{test_method} -v
+pytest tests/ --cov={source_dir} --cov-report=term-missing
+```
+
+### If `platform_type = web-frontend`
+
+```bash
+# Run all tests
+{conventions.test_command}
+
+# Scoped (Vitest / Jest):
+npx vitest run src/features/{domain}/{Component}.test.tsx
+npx jest src/features/{domain}/{Component}.test.tsx
+
+# E2E (Playwright):
+npx playwright test {UC-ID}
+# E2E (Cypress):
+npx cypress run --spec "cypress/e2e/{UC-ID}*"
+```
+
+### If `platform_type = mobile`
+
+```bash
+# Flutter:
+flutter test test/{domain}/{UC-ID}_test.dart
+flutter test integration_test/{UC-ID}_test.dart   # integration
+
+# React Native:
+npx jest {UC-ID}
+
+# iOS (Xcode command line):
+xcodebuild test -scheme {Scheme} -destination 'platform=iOS Simulator,name=iPhone 15'
+
+# Android:
+./gradlew test                              # unit tests
+./gradlew connectedAndroidTest              # instrumented (device/emulator required)
 ```
 
+> **Note for Android instrumented tests:** a running emulator or connected device is required before running `connectedAndroidTest`. Start one via Android Studio or: `emulator -avd {AVD_NAME} &`
+
+---
+
 ## Analyze Failures
 
+### Backend failure patterns
+
+#### java-spring / golang / dotnet / php-laravel
+
+| Error Pattern | Common Cause | Suggested Fix |
+|---|---|---|
+| `NullPointerException` | Missing mock setup | Check `given(...)`/`coEvery`/`mockk` for null dependency |
+| `Bean not found` | Missing mock declaration | Add `@MockBean` / inject mock |
+| `Expected 200, got 401` | Missing auth setup | Add auth token/user to test context |
+| `Expected 200, got 400` | Request body fails validation | Check required fields in DTO |
+| `Expected 200, got 403` | Wrong role | Add correct role to test user |
+| `LazyInitializationException` | Lazy collection outside transaction | Add `@Transactional` or eager fetch |
+| `Mapper not found` | Code not compiled | Run build step before tests |
+| `DataIntegrityViolationException` | Duplicate key in DB setup | Use `@Transactional` + rollback, or clean DB between tests |
+| Assertion mismatch | Wrong mock return value | Re-read `given(...).willReturn(...)` setup |
+
+#### context-engineering (AI/LLM pipelines)
+
+| Error Pattern | Common Cause | Suggested Fix |
+|---|---|---|
+| `AssertionError` on LLM mock output | Mock return value not matching schema | Re-check `mock_llm.return_value` / `mock_llm.complete.return_value` setup |
+| `ValidationError` on response | LLM output structure doesn't match expected schema | Tighten schema check or add retry logic in test |
+| `ConnectionError` / `APIError` | Real LLM API being called in test | Ensure `patch('...')` mock is applied — never call real LLM in unit tests |
+| `TimeoutError` | Test calling live LLM endpoint | Add mock; check test fixtures |
+| Flaky / non-deterministic results | Real LLM response used in assertion | Replace with deterministic mock return value |
+
+### Web frontend failure patterns
+
 | Error Pattern | Common Cause | Suggested Fix |
 |---|---|---|
-| NullPointerException | Missing mock setup | Check `given(...)` for null dependency |
-| Bean not found | Missing mock declaration | Add mock for missing dependency |
-| Expected 200, got 403 | Missing auth setup | Add auth user/role to test context |
-| Expected 200, got 400 | Request body fails validation | Check required fields in DTO |
-| LazyInitializationException | Lazy collection outside transaction | Add `@Transactional` or eager fetch |
-| Mapper not found | Code generator not run | Run compile step before tests |
+| `Unable to find role "..."` | Element not rendered yet | Wrap in `await waitFor(() => ...)` |
+| `TestingLibraryElementError: Found multiple elements` | Selector too broad | Use `getByRole(..., { name: '...' })` to narrow |
+| `Network request not intercepted` | Missing MSW handler / `cy.intercept` | Add handler for the endpoint |
+| `act(...)` warning | State update after test ended | Await async events / `await userEvent.click(...)` |
+| `Cannot read properties of undefined` | Component rendered before data loaded | Add loading state or mock resolved data |
+| Playwright timeout | Page not navigated / element hidden | Check route, add `waitForSelector` |
+| `expect(page.locator(...)).toBeVisible` fails | Wrong selector | Use Playwright Inspector to find correct locator |
+
+### Mobile failure patterns
+
+#### Flutter
+| Error Pattern | Common Cause | Suggested Fix |
+|---|---|---|
+| `pumpAndSettle timed out` | Async operation not completing | Use `pump(Duration(...))` for specific delay |
+| `No widget found` | Widget not rendered / wrong finder | Check `find.byType`, `find.text`, `find.byKey` |
+| `setState called after dispose` | Widget disposed before async completes | Cancel async in `dispose()` |
+| BLoC state mismatch | Wrong event emitted | Verify `mockBloc` received correct event |
+
+#### React Native
+| Error Pattern | Common Cause | Suggested Fix |
+|---|---|---|
+| `Unable to find element` | Missing `testID` or wrong query | Add `accessibilityLabel` or `testID` to component |
+| `act(...)` warning | Async state updates | Wrap in `act(async () => { ... })` |
+| Navigation mock missing | `useNavigation` not mocked | Add jest mock for `@react-navigation/native` |
+
+#### iOS / Android
+| Error Pattern | Common Cause | Suggested Fix |
+|---|---|---|
+| `XCTAssertEqual failed` | Wrong expected value | Check ViewModel output for given mock |
+| `Compose node not found` | Wrong `contentDescription` / `testTag` | Add `Modifier.testTag(...)` to composable |
+| `Hilt injection failed` | Missing test module | Add `@UninstallModules` + `@BindValue` in test class |
+| Emulator not available | `connectedAndroidTest` without device | Start emulator first, wait for it to boot |
+
+---
 
 ## Output
 
@@ -302,6 +440,7 @@ Suggest the logical next command based on workflow phase:
 
 | Current command         | Suggest next                                  |
 |-------------------------|-----------------------------------------------|
+| /setup-ai-first         | `/define-product` to start your first feature |
 | /define-product         | `/generate-prd {product-definition-file}`     |
 | /generate-prd           | `/refine-prd {prd-file}` then `/review-context {prd-file}` |
 | /refine-prd             | Open Review Board → update PRD → `/review-context {prd-file}` |
@@ -310,13 +449,13 @@ Suggest the logical next command based on workflow phase:
 | /review-context (BDD)   | `/generate-tech-docs {UC-ID}` if APPROVED; regenerate if NEEDS_FIX |
 | /generate-tech-docs     | `/review-tech-docs {tech-design-file}`        |
 | /review-tech-docs       | `/generate-code {feature-file}` if APPROVED; fix doc if NEEDS_FIX |
-| /generate-code          | `/generate-tests {UC-ID}`                     |
+| /generate-code          | First gen → `/review-code {UC-ID}`; re-gen → `/generate-tests {UC-ID}` |
 | /generate-tests         | `/run-tests {UC-ID}`                          |
 | /run-tests (passing)    | `/review-code {UC-ID}`                        |
 | /run-tests (failing)    | `/fix-bug {ticket-id}` or `/debug {error}`    |
 | /review-code            | `/smoke-test {UC-ID}` or create PR            |
 | /smoke-test             | Create PR and link to ticket                  |
-| /validate-traces        | `/generate-code {UC-ID}` for gaps             |
+| /validate-traces        | DRIFT/UNTRACKED → `/generate-code {UC-ID}`; GAP → `/generate-tests {UC-ID}`; all OK → create PR |
 | /fix-bug                | Create PR and link to ticket                  |
 | /debug                  | `/fix-bug {ticket-id}` if fix needed          |
 
@@ -330,14 +469,17 @@ Next   : {suggested command with example arguments}
 
 
 ```
-/run-tests Report — {service}
+/run-tests Report — {UC-ID} ({active_module})
 ✅ Passed: {N} | ❌ Failed: {M} | ⏭️ Skipped: {K} | Duration: {X}s
 
 ## Failed Tests
 | Test | Error | Root Cause |
-|------|-------|-----------|
+|------|-------|------------|
 
 ## Recommendations
 {specific fix per failure}
-Next: /fix-bug if real bug, or correct test if wrong expectation.
+
+Next:
+  All tests pass → /review-code {UC-ID}
+  Tests fail     → /fix-bug {TICKET_ID} (real bug) or fix test (wrong expectation)
 ```

package/core/commands/setup-ai-first.md

@@ -33,7 +33,7 @@ Display and wait for response:
 ```
 ⚙️  MODEL CHECK
 ──────────────────────────────────────────────────────────────────
-  Recommended  : claude-opus-4-5 (or claude-opus-4)
+  Recommended  : claude-opus-4 (or latest Opus model)
   Why needed   : Spec analysis, architecture review, code generation
                  require deep reasoning. Smaller models miss edge cases.
 
@@ -108,8 +108,8 @@ Create these directories (skip if they exist):
 │   ├── product-definition/
 │   ├── prd/
 │   ├── bdd/
+│   ├── tech-docs/            ← technical design documents
 │   └── domain-knowledge/     ← business dictionary & domain context
-├── tech-docs/
 ├── .trace/
 └── .agent/
     └── review/
@@ -153,7 +153,7 @@ forbidden:
 # §4. Traceability
 # Every controller method must be tagged:
 # @trace.implements={UC-ID}-{SC-ID}
-# @trace.source=specs/bdd/{domain}/{UC-ID}.feature
+# @trace.source=specs/bdd/{domain}/{UC-ID}.feature  ← adjust if specs_dir differs in .agent/project-context.yaml
 # Tests must be tagged:
 # @trace.verifies={UC-ID}
 
@@ -273,6 +273,8 @@ Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"**
 ## Step 7 — Verify
 
 - [ ] `specs/` exists
+- [ ] `specs/bdd/` exists
+- [ ] `specs/tech-docs/` exists
 - [ ] `specs/domain-knowledge/` exists
 - [ ] `.trace/` exists
 - [ ] `.agent/project-context.yaml` exists
@@ -282,6 +284,62 @@ Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"**
 
 ## Output
 
+# Report Footer — Standard Command Output Format
+
+Every command report must end with this standard footer section.
+
+## Status Badge
+
+Choose one based on outcome:
+- `✅ Complete` — all steps succeeded, no issues found
+- `❌ Failed` — command could not complete due to a blocking error
+- `⚠️ Warnings` — completed with non-blocking issues that should be reviewed
+
+## Output Artifacts
+
+List every file created or modified by this command:
+```
+Output Artifacts:
+  {created|updated} {file-path} ({brief description})
+  {created|updated} {file-path} ({brief description})
+```
+
+If no files were written (e.g., review or analysis commands) → write `Output Artifacts: none (read-only)`.
+
+## Next Command Suggestion
+
+Suggest the logical next command based on workflow phase:
+
+| Current command         | Suggest next                                  |
+|-------------------------|-----------------------------------------------|
+| /setup-ai-first         | `/define-product` to start your first feature |
+| /define-product         | `/generate-prd {product-definition-file}`     |
+| /generate-prd           | `/refine-prd {prd-file}` then `/review-context {prd-file}` |
+| /refine-prd             | Open Review Board → update PRD → `/review-context {prd-file}` |
+| /review-context (PRD)   | `/generate-bdd {prd-file}` if APPROVED; fix PRD if NEEDS_FIX |
+| /generate-bdd           | `/review-context {feature-file}` to verify coverage |
+| /review-context (BDD)   | `/generate-tech-docs {UC-ID}` if APPROVED; regenerate if NEEDS_FIX |
+| /generate-tech-docs     | `/review-tech-docs {tech-design-file}`        |
+| /review-tech-docs       | `/generate-code {feature-file}` if APPROVED; fix doc if NEEDS_FIX |
+| /generate-code          | First gen → `/review-code {UC-ID}`; re-gen → `/generate-tests {UC-ID}` |
+| /generate-tests         | `/run-tests {UC-ID}`                          |
+| /run-tests (passing)    | `/review-code {UC-ID}`                        |
+| /run-tests (failing)    | `/fix-bug {ticket-id}` or `/debug {error}`    |
+| /review-code            | `/smoke-test {UC-ID}` or create PR            |
+| /smoke-test             | Create PR and link to ticket                  |
+| /validate-traces        | DRIFT/UNTRACKED → `/generate-code {UC-ID}`; GAP → `/generate-tests {UC-ID}`; all OK → create PR |
+| /fix-bug                | Create PR and link to ticket                  |
+| /debug                  | `/fix-bug {ticket-id}` if fix needed          |
+
+Format the footer as:
+```
+---
+Status : {badge}
+{Output Artifacts block}
+Next   : {suggested command with example arguments}
+```
+
+
 ```
 /setup-ai-first Complete ✅
 Next:

package/core/commands/smoke-test.md

@@ -1,6 +1,6 @@
-# /smoke-test — Test Live API Endpoints
+# /smoke-test — Smoke Test Live Service or App
 
-Use when service is **already running**. Different from `/run-tests` (no live server needed).
+Use when service/app is **already running**. Different from `/run-tests` (no live server needed).
 
 ## Gate
 # Gate — Universal Entry Procedure
@@ -33,7 +33,7 @@ Display and wait for response:
 ```
 ⚙️  MODEL CHECK
 ──────────────────────────────────────────────────────────────────
-  Recommended  : claude-opus-4-5 (or claude-opus-4)
+  Recommended  : claude-opus-4 (or latest Opus model)
   Why needed   : Spec analysis, architecture review, code generation
                  require deep reasoning. Smaller models miss edge cases.
 
@@ -86,7 +86,7 @@ Wait for explicit "Y" or "N" from the user before continuing.
 - "N" → stop and ask what the user wants to change.
 
 
-*Note: For this command, the target in Step 1 is a UC-ID from `$ARGUMENTS`. Context loading provides `conventions.service_run` and port information.*
+*Note: For this command, the target in Step 1 is a UC-ID from `$ARGUMENTS`. Context loading provides `conventions.service_run`, port information, and `tech_stack.module`.*
 
 ## Context
 # Context Loader — Load All Project Context
@@ -142,7 +142,7 @@ If `paths` section is absent, use these defaults:
 - `domain_knowledge_dir` = `specs/domain-knowledge`
 - `business_dictionary` = `specs/domain-knowledge/business-dictionary.md`
 - `core_entities` = `specs/domain-knowledge/core-entities.md`
-- `tech_docs_dir` = `tech-docs`
+- `tech_docs_dir` = `specs/tech-docs`
 - `trace_dir` = `.trace`
 
 If `tech_stack.module` is set, also load `.agent/modules/{module}/stack-profile.yaml` if it exists.
@@ -219,6 +219,26 @@ If the file does not exist → skip silently.
 
 ---
 
+## Step 6.5 — [PLATFORM] Derive active_module and platform_type
+
+Using `tech_stack.module` loaded in Step 1, derive and store two variables for use by all downstream commands:
+
+```
+active_module = tech_stack.module   (e.g. "java-spring", "react", "flutter")
+```
+
+| `platform_type` | Modules |
+|---|---|
+| `backend` | `java-spring`, `golang`, `dotnet`, `php-laravel`, `context-engineering` |
+| `web-frontend` | `react`, `nextjs`, `vue`, `nuxt`, `angular` |
+| `mobile` | `flutter`, `react-native`, `ios-swiftui`, `android-compose` |
+
+If `tech_stack.module` is blank or not recognized → set `platform_type = "unknown"` and flag as ⚠️ in the Step 7 recap.
+
+These two variables (`active_module`, `platform_type`) are the canonical source for all branching logic in commands that need platform-specific behavior (generate-tests, debug, fix-bug, smoke-test).
+
+---
+
 ## Step 7 — [RECAP] Working Memory Recap (anti-lost-in-middle)
 
 After loading all context, synthesize and output a compact summary block.
@@ -229,6 +249,7 @@ Output exactly this block:
 ```
 [CTX LOADED]
 Stack     : {language} / {framework} / {database}
+Platform  : {active_module} ({platform_type})
 Layers    : {layer order from CLAUDE.md §2, e.g., Controller → Facade → Service → Repository}
 Ticket    : {ticket_prefix}-
 Dict      : {loaded — N canonical terms, M banned terms | missing}
@@ -256,19 +277,40 @@ Proceed to the next step of the calling command.
 
 ---
 
-## Phase 1 — Find Service URL
+## Service Detection
+
+Read `active_module` from context. Use to select the correct smoke-test approach.
+
+| Platform | Modules |
+|---|---|
+| `backend` | `java-spring`, `golang`, `dotnet`, `php-laravel`, `context-engineering` |
+| `web-frontend` | `react`, `nextjs`, `vue`, `nuxt`, `angular` |
+| `mobile` | `flutter`, `react-native`, `ios-swiftui`, `android-compose` |
+
+---
+
+## If `platform_type = backend`
+
+### Phase 1 — Verify service is running
+
 Read `conventions.service_run` from project-context.yaml to determine port.
+
 ```bash
-curl -s http://localhost:{port}/health
+# Try common health endpoints (use whichever applies):
+curl -s http://localhost:{port}/health            # generic / Go / Node
+curl -s http://localhost:{port}/actuator/health   # Spring Boot
+curl -s http://localhost:{port}/ping              # some frameworks
 ```
-If not running: "Start with `{conventions.service_run}` from project root."
 
-## Phase 2 — Identify Endpoints
-From UC-ID (or `$ARGUMENTS`) → find controller with `@trace.implements={UC-ID}`.
+If not running → "Start with `{conventions.service_run}` from project root."
+
+### Phase 2 — Identify endpoints
+
+From UC-ID → find controller/handler with `@trace.implements={UC-ID}`.
 List: method, path, required auth/role.
 
-## Phase 3 — Get Auth Token (if needed)
-Ask:
+### Phase 3 — Get auth token (if needed)
+
 ```
 Endpoint requires auth. Options:
 1. Paste Bearer token (from Postman/DevTools)
@@ -276,10 +318,11 @@ Endpoint requires auth. Options:
 3. Skip — test public endpoints only
 ```
 
-## Phase 4 — Run Smoke Test
+### Phase 4 — Run
+
 ```bash
 # GET
-curl -s -X GET "http://localhost:{port}/v1/{resource}?page=0&size=5" \
+curl -s -X GET "http://localhost:{port}/v1/{resource}" \
   -H "Authorization: Bearer {token}" | {JSON_FORMATTER}
 
 # POST
@@ -289,7 +332,6 @@ curl -s -X POST "http://localhost:{port}/v1/{resource}" \
   -d '{"field1": "test_value"}'
 ```
 
-## Interpret Results
 | Result | Meaning |
 |--------|---------|
 | 200/201 + correct data | ✅ OK |
@@ -297,9 +339,131 @@ curl -s -X POST "http://localhost:{port}/v1/{resource}" \
 | 400 | Wrong request body → check required fields |
 | 401 | Token expired or wrong config |
 | 403 | Wrong role → check auth rules |
-| 500 | Server error → paste into /debug |
+| 500 | Server error → /debug |
 | Connection refused | Service not running |
 
+### If `active_module = context-engineering`
+
+#### Phase 1 — Verify pipeline entry point is reachable
+
+Run the prompt function directly with a minimal valid input:
+
+```bash
+# Python (pytest / script):
+python -c "from {module}.{function} import {function}; print({function}(input='{test_input}'))"
+
+# Or using the project test command with a smoke marker:
+{conventions.test_command} -m smoke -v
+```
+
+#### Phase 2 — Verify output structure
+
+Check the output conforms to the expected schema:
+
+```
+Expected output schema: {output fields from @trace or tech-doc}
+Actual output: {paste output here}
+```
+
+#### Phase 3 — Interpret results
+
+| Result | Meaning |
+|--------|---------|
+| Output matches schema | ✅ OK |
+| Output present but wrong format | ⚠️ Logic bug → /debug |
+| `APIError` / `AuthenticationError` | API key invalid or service unavailable |
+| `TokenLimitError` | Input too long — check prompt template size |
+| Exception / traceback | Code error → /debug |
+
+---
+
+## If `platform_type = web-frontend`
+
+### Phase 1 — Verify dev server is running
+
+```bash
+# Linux / macOS:
+curl -s -o /dev/null -w "%{http_code}" http://localhost:{port}
+
+# Windows (cmd / PowerShell):
+curl -s -o NUL -w "%{http_code}" http://localhost:{port}
+
+# Should return 200. If not: start with {conventions.service_run} (e.g., npm run dev)
+```
+
+### Phase 2 — Run E2E smoke test
+
+Identify E2E tool in the project (Playwright or Cypress):
+
+```bash
+# Playwright — run scenarios tagged with this UC:
+npx playwright test --grep "{UC-ID}"
+
+# Cypress:
+npx cypress run --spec "cypress/e2e/{UC-ID}*"
+```
+
+If no E2E tests exist yet → open browser and manually verify:
+1. Navigate to the route for this UC
+2. Perform the main user action
+3. Confirm the expected outcome is visible
+
+### Phase 3 — Interpret results
+
+| Result | Meaning |
+|--------|---------|
+| All E2E tests pass | ✅ OK |
+| Assertion failed | ⚠️ Logic bug → /debug |
+| `ERR_CONNECTION_REFUSED` | Dev server not running |
+| API returns 4xx/5xx | Backend issue → check backend service |
+
+---
+
+## If `platform_type = mobile`
+
+### Phase 1 — Verify device/emulator is ready
+
+```bash
+# Flutter:
+flutter devices              # list connected devices/emulators
+flutter install              # install current build on device
+
+# React Native:
+npx react-native run-android   # build + install on connected Android
+npx react-native run-ios       # build + install on iOS simulator
+
+# Android (Compose):
+./gradlew installDebug         # install APK on connected device/emulator
+
+# iOS (SwiftUI):
+# Open Xcode → select simulator → Product → Run
+```
+
+### Phase 2 — Manual smoke-test checklist
+
+For the UC under test, verify on device:
+1. Navigate to the screen for this UC
+2. Perform the main action from the `.feature` Scenario (`When` step)
+3. Confirm the expected outcome is visible (`Then` step)
+4. Check for any crash or unexpected error dialog
+
+### Phase 3 — Capture issues if found
+
+```bash
+# Flutter:
+flutter logs
+
+# Android:
+adb logcat -d | grep -i "error\|exception\|crash"
+
+# iOS:
+# Copy crash log from Xcode → Devices and Simulators → View Device Logs
+```
+
+Paste output into `/debug`.
+
+---
+
 ## Output
 
 # Report Footer — Standard Command Output Format
@@ -330,6 +494,7 @@ Suggest the logical next command based on workflow phase:
 
 | Current command         | Suggest next                                  |
 |-------------------------|-----------------------------------------------|
+| /setup-ai-first         | `/define-product` to start your first feature |
 | /define-product         | `/generate-prd {product-definition-file}`     |
 | /generate-prd           | `/refine-prd {prd-file}` then `/review-context {prd-file}` |
 | /refine-prd             | Open Review Board → update PRD → `/review-context {prd-file}` |
@@ -338,13 +503,13 @@ Suggest the logical next command based on workflow phase:
 | /review-context (BDD)   | `/generate-tech-docs {UC-ID}` if APPROVED; regenerate if NEEDS_FIX |
 | /generate-tech-docs     | `/review-tech-docs {tech-design-file}`        |
 | /review-tech-docs       | `/generate-code {feature-file}` if APPROVED; fix doc if NEEDS_FIX |
-| /generate-code          | `/generate-tests {UC-ID}`                     |
+| /generate-code          | First gen → `/review-code {UC-ID}`; re-gen → `/generate-tests {UC-ID}` |
 | /generate-tests         | `/run-tests {UC-ID}`                          |
 | /run-tests (passing)    | `/review-code {UC-ID}`                        |
 | /run-tests (failing)    | `/fix-bug {ticket-id}` or `/debug {error}`    |
 | /review-code            | `/smoke-test {UC-ID}` or create PR            |
 | /smoke-test             | Create PR and link to ticket                  |
-| /validate-traces        | `/generate-code {UC-ID}` for gaps             |
+| /validate-traces        | DRIFT/UNTRACKED → `/generate-code {UC-ID}`; GAP → `/generate-tests {UC-ID}`; all OK → create PR |
 | /fix-bug                | Create PR and link to ticket                  |
 | /debug                  | `/fix-bug {ticket-id}` if fix needed          |
 
@@ -359,8 +524,13 @@ Next   : {suggested command with example arguments}
 
 ```
 /smoke-test Report — {UC-ID}
-| Method | Path | Status | Result |
-|--------|------|--------|--------|
+Platform: {backend | web-frontend | mobile}
+| Endpoint / Flow       | Status      | Result  |
+|-----------------------|-------------|---------|
+| {method} {path/screen}| ✅/⚠️/❌   | {notes} |
+
+Status legend: ✅ = OK  |  ⚠️ = Responded but wrong data / logic bug  |  ❌ = Error / not running
+
 Issues: {describe any failures}
-Next: /debug {stacktrace} OR /fix-bug {TICKET_ID} OR ready to PR
+Next: /debug (paste error interactively) OR /fix-bug {TICKET_ID} OR ready to PR
 ```