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

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.
 
@@ -98,6 +98,51 @@ Check if already set up:
   - Y → continue (existing files will be preserved — each step will offer merge/skip)
 - If only `specs/` exists or only partial setup detected → continue normally (safe to re-run)
 
+## Step 0.5 — Project Type
+
+Ask the user:
+
+```
+What type of project is this?
+  1. Single-service  — one codebase, one platform (standard setup)
+  2. Umbrella repo   — this repo contains multiple service submodules (microservices / multi-app)
+  3. PO Spec repo    — docs only, no runnable code (PRD + design-spec only)
+```
+
+Store the answer as `project_type`. Default to `1` if user does not answer.
+
+Based on answer:
+
+**project_type = 1 (Single-service):** Continue standard setup below.
+
+**project_type = 2 (Umbrella):** Ask two follow-up questions:
+- "Path to spec submodule (e.g. `free-trial-specs`)? Press Enter to skip."
+- "List services as `domain:module` pairs, comma-separated
+  (e.g. `user:java-spring,order:java-spring`). Press Enter to skip."
+
+Then:
+- Skip creating `specs/prd/`, `specs/design-spec/`, `specs/domain-knowledge/` (those live in spec submodule)
+- Create only: `specs/bdd/`, `specs/tech-docs/`, `.trace/`, `.agent/review/` at umbrella level
+  *(Unless user explicitly asks to create the full structure)*
+- Generate `.agent/project-context.yaml` in umbrella mode with the services and spec_source provided
+- Skip creating `CLAUDE.md` (umbrella has no single tech stack)
+- After setup, remind: "Open each service submodule separately in Claude Code to install the framework there if needed."
+
+**project_type = 3 (PO Spec repo):**
+- Create: `specs/prd/`, `specs/design-spec/`, `specs/product-definition/`, `specs/domain-knowledge/`, `.agent/review/`
+- Skip: `specs/bdd/`, `specs/tech-docs/`, `.trace/`
+- Generate minimal `CLAUDE.md` with only §1 (project overview) and §7 (git conventions)
+- Ask the user: **"List your business domains (e.g. auth, payment, loyalty):"** — store as domain list for `project-context.yaml` and remind PO these names must be used consistently as `@trace.domain` in every PRD
+- Inform:
+  - Commands for PO repo: `/define-product`, `/generate-prd`, `/review-context`, `/generate-design-spec`
+  - **Critical for dev team handoff:** Every PRD must have `@trace.domain: {domain}` in its frontmatter. Dev team uses this to route generated BDD/code to the correct service submodule. Inconsistent domain names will break routing.
+  - Recommended PRD frontmatter:
+    ```
+    @trace.domain: {domain}    ← must match a key in dev team's services config
+    @trace.id: {TICKET-ID}
+    @trace.status: draft | approved
+    ```
+
 ## Step 1 — Create Directory Structure
 
 Create these directories (skip if they exist):
@@ -108,15 +153,27 @@ Create these directories (skip if they exist):
 │   ├── product-definition/
 │   ├── prd/
 │   ├── bdd/
+│   ├── design-spec/          ← Design Spec documents (FE/App platforms only)
+│   ├── tech-docs/            ← technical design documents
 │   └── domain-knowledge/     ← business dictionary & domain context
-├── tech-docs/
 ├── .trace/
 └── .agent/
     └── review/
 ```
 
+*Directory structure varies by `project_type` set in Step 0.5:*
+
+| project_type | Create | Skip |
+|---|---|---|
+| **1 — Single-service** | Full structure above | — |
+| **2 — Umbrella** | `.agent/review/` only (at umbrella root) | Everything else — `specs/` dirs live inside service submodules |
+| **3 — PO Spec repo** | `specs/prd/`, `specs/design-spec/`, `specs/product-definition/`, `specs/domain-knowledge/`, `.agent/review/` | `specs/bdd/`, `specs/tech-docs/`, `.trace/` |
+
 ## Step 2 — Create CLAUDE.md
 
+*Skip this step entirely if `project_type = 2` (Umbrella) — umbrella has no single tech stack.*
+*For `project_type = 3` (PO Spec repo) — create a minimal CLAUDE.md with only §1 (project overview) and §7 (git conventions). Skip §2–§6.*
+
 Check if `CLAUDE.md` exists:
 - Yes → ask "Merge template or skip?"
 - No → create from the template below
@@ -153,7 +210,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}
 
@@ -173,12 +230,19 @@ commit_feature: "feat({{TICKET_PREFIX}}-{N}): {description}"
 
 ## Step 3 — Create project-context.yaml
 
+*For `project_type = 2` (Umbrella):*
+- *If `.agent/project-context.yaml` was already generated by `--init --umbrella` → open it and verify/edit the `services` section (domain keys, paths, modules). Skip template copy below.*
+- *If not yet generated → ask: "Spec submodule path?" and "Services (domain:module pairs)?" then generate umbrella config (see Step 0.5 for format).*
+
 Create `.agent/project-context.yaml` using `.agent/templates/project-context.yaml` as the source template.
 
 Copy the template and instruct: "Open `.agent/project-context.yaml` and fill in all `{{PLACEHOLDER}}` values. The `paths` section is pre-configured with sensible defaults — adjust if your project uses different directory names."
 
 ## Step 4 — Create business-dictionary.md
 
+*Skip Steps 4 and 5 if `project_type = 2` (Umbrella) — business dictionary and core entities live in the spec submodule and are managed by the PO team. Dev team reads them from `{spec_source}/specs/domain-knowledge/`.*
+
+
 Create `specs/domain-knowledge/business-dictionary.md` if it does not exist:
 
 ```markdown
@@ -272,7 +336,13 @@ Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"**
 
 ## Step 7 — Verify
 
+Checklist varies by `project_type`:
+
+**project_type = 1 (Single-service):**
 - [ ] `specs/` exists
+- [ ] `specs/bdd/` exists
+- [ ] `specs/design-spec/` exists *(skip if backend-only project)*
+- [ ] `specs/tech-docs/` exists
 - [ ] `specs/domain-knowledge/` exists
 - [ ] `.trace/` exists
 - [ ] `.agent/project-context.yaml` exists
@@ -280,17 +350,133 @@ Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"**
 - [ ] `specs/domain-knowledge/business-dictionary.md` exists
 - [ ] `specs/domain-knowledge/core-entities.md` exists
 
+**project_type = 2 (Umbrella):**
+- [ ] `.agent/project-context.yaml` exists with `setup.mode: umbrella`
+- [ ] `services` section has at least one entry with correct domain keys
+- [ ] `spec_source` path exists (e.g., `my-project-specs/` directory is present)
+- [ ] `.agent/review/` exists
+- [ ] Spec submodule initialized: `git submodule status` shows no `-` prefix
+
+**project_type = 3 (PO Spec repo):**
+- [ ] `specs/prd/` exists
+- [ ] `specs/design-spec/` exists
+- [ ] `specs/product-definition/` exists
+- [ ] `specs/domain-knowledge/` exists
+- [ ] `.agent/review/` exists
+- [ ] `.agent/project-context.yaml` exists
+- [ ] `CLAUDE.md` exists (minimal)
+- [ ] `specs/domain-knowledge/business-dictionary.md` exists
+- [ ] `specs/domain-knowledge/core-entities.md` exists
+
 ## 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)   | FE/App: `/generate-design-spec {prd-file}` (then BDD after sign-off); BE: `/generate-bdd {prd-file}` directly; fix PRD if NEEDS_FIX |
+| /generate-design-spec   | Designer review → Figma links confirmed → PO + Designer sign-off → `/generate-bdd {prd-file}` |
+| /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 ✅
+```
+
+Output varies by `project_type`:
+
+**Single-service:**
+```
 Next:
   1. Fill CLAUDE.md (replace {{PLACEHOLDER}} values)
   2. Fill .agent/project-context.yaml
-  3. Fill specs/domain-knowledge/business-dictionary.md  ← terminology rules
-  4. Fill specs/domain-knowledge/core-entities.md        ← entity glossary for code gen
+  3. Fill specs/domain-knowledge/business-dictionary.md
+  4. Fill specs/domain-knowledge/core-entities.md
   5. git add and commit those 4 files
-  6. Install VS Code extension (if not yet installed):
+  6. Install VS Code extension:
      code --install-extension edupia-team.spec-driven-dev-team
   7. /define-product to start your first feature
 ```
+
+**Umbrella:**
+```
+Next:
+  1. Review .agent/project-context.yaml:
+     - Update services[].path to match actual submodule directory names
+     - Update services domain keys to match @trace.domain in your PRD files
+     - Confirm spec_source path is correct
+  2. Ensure spec submodule is initialized:
+     git submodule update --init --recursive
+  3. Pull latest specs from PO before generating:
+     git submodule update --remote {spec_source}
+  4. Start generating:
+     /generate-bdd {spec_source}/specs/prd/{domain}/TICKET-ID-prd.md
+```
+
+**PO Spec repo:**
+```
+Next:
+  1. Fill .agent/project-context.yaml:
+     - domains: [list all business domains — these become @trace.domain values in PRDs]
+     - project.name, project.description
+  2. Fill specs/domain-knowledge/business-dictionary.md  ← canonical terms
+  3. Fill specs/domain-knowledge/core-entities.md        ← entity glossary
+  4. git add and commit those files
+  5. Install VS Code extension:
+     code --install-extension edupia-team.spec-driven-dev-team
+  6. /define-product to start your first feature
+
+⚠️  Dev team handoff reminder:
+  - Each PRD must have @trace.domain matching one of your domains list
+  - When dev team sets up their umbrella repo, they map these domain names
+    to service submodule paths in their project-context.yaml services section
+  - Share domain names with dev team before they configure their umbrellas
+```

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
@@ -133,6 +133,7 @@ Read `.agent/project-context.yaml`. Extract and store:
 - `paths.core_entities` → path to core-entities.md
 - `paths.tech_docs_dir` → technical documentation root
 - `paths.trace_dir` → trace state directory
+- `paths.design_spec_dir` → Design Spec documents root (FE/App only)
 
 If `paths` section is absent, use these defaults:
 - `specs_dir` = `specs/bdd`
@@ -142,13 +143,46 @@ 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`
+- `design_spec_dir` = `specs/design-spec`
 
 If `tech_stack.module` is set, also load `.agent/modules/{module}/stack-profile.yaml` if it exists.
 
 ---
 
+## Step 1.5 — [SERVICE ROUTING] Resolve service paths (umbrella mode)
+
+*Skip this step entirely if `setup.mode` is not `"umbrella"` and `services` section is absent from project-context.yaml.*
+
+If `services` section is present:
+
+**1. Detect active domain** (in priority order):
+- Read `@trace.domain` from target file frontmatter (if Gate loaded a target file)
+- Extract from target file path: segment immediately after `prd_dir` base path  
+  *(e.g., `specs/prd/user/FEAT-01.md` → domain = `user`)*
+- If `$ARGUMENTS` contains a path, extract the segment after `prd_dir`
+
+**2. Route to service** — if active domain matches a key in `services`:
+- Override `paths.specs_dir` → `services.{domain}.specs_dir`
+- Override `paths.tech_docs_dir` → `services.{domain}.tech_docs_dir`
+- Store `active_service` = `services.{domain}.path`
+- Store `active_service_module` = `services.{domain}.module`
+- If service has its own `module` → use it as `active_module` (overrides `tech_stack.module`)
+
+**3. Fallback** — if domain not detected or no matching service key:
+- Keep default paths from Step 1
+- Set `active_service = unresolved`
+
+**4. Spec source auto-override** — if `setup.spec_source` is set AND the corresponding path was not already explicitly set in `paths:`:
+- Override `paths.prd_dir` → `{spec_source}/specs/prd`
+- Override `paths.design_spec_dir` → `{spec_source}/specs/design-spec`
+- Override `paths.domain_knowledge_dir` → `{spec_source}/specs/domain-knowledge`
+- Override `paths.business_dictionary` → `{spec_source}/specs/domain-knowledge/business-dictionary.md`
+- Override `paths.core_entities` → `{spec_source}/specs/domain-knowledge/core-entities.md`
+
+---
+
 ## Step 2 — [PROJECT-CONFIG] Load module stack profile (conditional)
 
 If `tech_stack.module` is set, read `.agent/modules/{module}/stack-profile.yaml`.
@@ -219,6 +253,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,10 +283,12 @@ 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}
 Entities  : {loaded — EntityA, EntityB, EntityC | missing}
+Service   : {active_service} ({active_service_module}) | single-service
 Status    : {FULL | PARTIAL — missing: CLAUDE.md / business-dict / core-entities | MINIMAL}
 ```
 
@@ -256,19 +312,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 +353,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 +367,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 +374,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,21 +529,23 @@ 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 |
+| /review-context (PRD)   | FE/App: `/generate-design-spec {prd-file}` (then BDD after sign-off); BE: `/generate-bdd {prd-file}` directly; fix PRD if NEEDS_FIX |
+| /generate-design-spec   | Designer review → Figma links confirmed → PO + Designer sign-off → `/generate-bdd {prd-file}` |
 | /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          | `/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 +560,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
 ```