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

package/commands/validate-traces.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.
 
@@ -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}
@@ -263,6 +284,13 @@ Proceed to the next step of the calling command.
 Read all `{paths.trace_dir}/{UC-ID}.tsv` files matching the target domain (or all domains if no domain filter).
 Each file gives the persisted trace state for that UC.
 
+**If no `.tsv` files found** in `{paths.trace_dir}`:
+- Scan all `{paths.specs_dir}/**/*.feature` files in the target domain to build an in-memory list of all scenarios.
+- Treat all scenarios as `UNTRACKED` (no code generated yet).
+- Print: "⚠️ No trace files found. All {N} scenarios across {M} UCs are UNTRACKED."
+- Suggest: "Run `/generate-bdd {prd-file}` to initialize trace state, or `/generate-code {feature-file}` to generate code."
+- **Skip Steps 2–6 entirely.** Proceed directly to Step 7 using this in-memory state — do NOT abort.
+
 ### Step 2 — Reconcile with current `.feature` files
 
 For each `.tsv` row, read the corresponding `.feature` file and get the **current** `@trace.sc_version` for that SC.
@@ -300,6 +328,8 @@ If code was generated from an older revision → flag `TECHDOC_DRIFT`.
 
 ### Step 6 — Write status back to TSV
 
+*Skip this step if no TSV files existed (handled by Step 1 no-TSV path).*
+
 For each `.tsv` file processed: write updated `spec_ver`, `status`, `last_updated` back to disk.
 
 ### Step 7 — Compute dashboard aggregates
@@ -309,6 +339,7 @@ total_prds       = count distinct PRD files in {paths.prd_dir}/{domain}/
 approved_prds    = PRDs with | Status | approved
 total_ucs        = count distinct UC-IDs across all .tsv files
 approved_ucs     = UCs with uc_status == approved
+draft_ucs        = UCs with uc_status == draft
 total_scs        = total rows across all .tsv files
 code_coverage    = rows where implemented_by != — / total_scs
 test_coverage    = rows where test_count > 0 / total_scs
@@ -320,7 +351,7 @@ tech_docs_count  = count .md files in {paths.tech_docs_dir}/{domain}/
 
 ### Step 8 — Write JSON report
 
-Write `.trace/trace-report.json` (overwrite if exists). This file is the single source of truth for web dashboards — it contains the full snapshot at the time `/validate-traces` was last run.
+Write `{paths.trace_dir}/trace-report.json` (overwrite if exists). This file is the single source of truth for web dashboards — it contains the full snapshot at the time `/validate-traces` was last run.
 
 Schema:
 
@@ -430,7 +461,8 @@ Schema:
 - `test_classes`: use `[]` (not `"—"`) when no test classes
 - `tech_doc_revision`: use integer; `0` if not yet generated
 - `code_coverage_pct` / `test_coverage_pct`: round to nearest integer (0–100)
-- Always write to `.trace/trace-report.json` regardless of domain filter — if a domain filter was applied, include only those PRDs in `prds[]` but note the domain in the `domain` field
+- Always write to `{paths.trace_dir}/trace-report.json` regardless of domain filter — if a domain filter was applied, include only those PRDs in `prds[]` but note the domain in the `domain` field
+- **TSV `"—"` mapping**: when reading TSV files, map dash values to JSON types: `implemented_by: "—"` → `null`; `test_count: "—"` → `0`; `test_classes: "—"` → `[]`; `tech_doc_revision: "—"` → `0`
 
 ## Output
 
@@ -462,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}` |
@@ -470,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          |
 
@@ -492,7 +525,7 @@ Next   : {suggested command with example arguments}
 ```
 /validate-traces — {domain}
 
-📄 .trace/trace-report.json  ← updated
+📄 {paths.trace_dir}/trace-report.json  ← updated
 
 ┌─────────────────────────────────────────────────────────────────────────────────────┐
 │  PRDs      Use Cases     Scenarios   Code Cov.  Test Cov.  Drift  Untracked  Gap   │

package/commands/validate-traces.tmpl

@@ -19,6 +19,13 @@ Read-only check of coverage between specs, code, and tests — including PRD ver
 Read all `{paths.trace_dir}/{UC-ID}.tsv` files matching the target domain (or all domains if no domain filter).
 Each file gives the persisted trace state for that UC.
 
+**If no `.tsv` files found** in `{paths.trace_dir}`:
+- Scan all `{paths.specs_dir}/**/*.feature` files in the target domain to build an in-memory list of all scenarios.
+- Treat all scenarios as `UNTRACKED` (no code generated yet).
+- Print: "⚠️ No trace files found. All {N} scenarios across {M} UCs are UNTRACKED."
+- Suggest: "Run `/generate-bdd {prd-file}` to initialize trace state, or `/generate-code {feature-file}` to generate code."
+- **Skip Steps 2–6 entirely.** Proceed directly to Step 7 using this in-memory state — do NOT abort.
+
 ### Step 2 — Reconcile with current `.feature` files
 
 For each `.tsv` row, read the corresponding `.feature` file and get the **current** `@trace.sc_version` for that SC.
@@ -56,6 +63,8 @@ If code was generated from an older revision → flag `TECHDOC_DRIFT`.
 
 ### Step 6 — Write status back to TSV
 
+*Skip this step if no TSV files existed (handled by Step 1 no-TSV path).*
+
 For each `.tsv` file processed: write updated `spec_ver`, `status`, `last_updated` back to disk.
 
 ### Step 7 — Compute dashboard aggregates
@@ -65,6 +74,7 @@ total_prds       = count distinct PRD files in {paths.prd_dir}/{domain}/
 approved_prds    = PRDs with | Status | approved
 total_ucs        = count distinct UC-IDs across all .tsv files
 approved_ucs     = UCs with uc_status == approved
+draft_ucs        = UCs with uc_status == draft
 total_scs        = total rows across all .tsv files
 code_coverage    = rows where implemented_by != — / total_scs
 test_coverage    = rows where test_count > 0 / total_scs
@@ -76,7 +86,7 @@ tech_docs_count  = count .md files in {paths.tech_docs_dir}/{domain}/
 
 ### Step 8 — Write JSON report
 
-Write `.trace/trace-report.json` (overwrite if exists). This file is the single source of truth for web dashboards — it contains the full snapshot at the time `/validate-traces` was last run.
+Write `{paths.trace_dir}/trace-report.json` (overwrite if exists). This file is the single source of truth for web dashboards — it contains the full snapshot at the time `/validate-traces` was last run.
 
 Schema:
 
@@ -186,7 +196,8 @@ Schema:
 - `test_classes`: use `[]` (not `"—"`) when no test classes
 - `tech_doc_revision`: use integer; `0` if not yet generated
 - `code_coverage_pct` / `test_coverage_pct`: round to nearest integer (0–100)
-- Always write to `.trace/trace-report.json` regardless of domain filter — if a domain filter was applied, include only those PRDs in `prds[]` but note the domain in the `domain` field
+- Always write to `{paths.trace_dir}/trace-report.json` regardless of domain filter — if a domain filter was applied, include only those PRDs in `prds[]` but note the domain in the `domain` field
+- **TSV `"—"` mapping**: when reading TSV files, map dash values to JSON types: `implemented_by: "—"` → `null`; `test_count: "—"` → `0`; `test_classes: "—"` → `[]`; `tech_doc_revision: "—"` → `0`
 
 ## Output
 
@@ -195,7 +206,7 @@ Schema:
 ```
 /validate-traces — {domain}
 
-📄 .trace/trace-report.json  ← updated
+📄 {paths.trace_dir}/trace-report.json  ← updated
 
 ┌─────────────────────────────────────────────────────────────────────────────────────┐
 │  PRDs      Use Cases     Scenarios   Code Cov.  Test Cov.  Drift  Untracked  Gap   │

package/core/FRAMEWORK_VERSION

@@ -1 +1 @@
-0.5.0
+0.7.0

package/core/commands/debug.md

@@ -34,7 +34,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.
 
@@ -143,7 +143,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.
@@ -220,6 +220,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.
@@ -230,6 +250,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}
@@ -257,13 +278,112 @@ Proceed to the next step of the calling command.
 
 ---
 
-## Input — Paste one of:
-1. Stack trace / error log
-2. Test failure output
-3. File path + description of unexpected behavior
-4. A specific question about a code snippet
+## Step 1 — Classify debug type
+
+After loading context, display this prompt and wait for the user's choice:
+
+```
+DEBUG SESSION
+──────────────────────────────────────────────────────────────
+  What's your situation?
+
+  1  I already have a stack trace / error log  → paste it
+  2  I need to reproduce the error first       → show me the run command
+  3  A test is failing                         → I'll run tests, then paste output
+  4  Code question (no runtime needed)         → ask away
+──────────────────────────────────────────────────────────────
+Enter 1 / 2 / 3 / 4:
+```
+
+Wait for the user's choice, then follow the corresponding path below.
+
+---
+
+### Path 1 — Already have error output
+
+Ask:
+```
+Paste your stack trace / error log below:
+```
+
+Wait for input, then proceed to [Stack Trace Analysis](#stack-trace-analysis).
+
+---
+
+### Path 2 — Need to reproduce first
+
+Display the run command from `conventions.service_run` in `project-context.yaml`:
+
+```
+Start your service first:
+
+  {conventions.service_run}
+
+(If you use Docker: `docker compose up -d`, then verify with `docker compose ps`)
+
+Once the service is running:
+  1. Trigger the behavior that causes the error
+  2. Copy the full stack trace or error log
+  3. Paste it here
+
+Waiting for your error output...
+```
+
+Wait for the user to paste the error, then proceed to [Stack Trace Analysis](#stack-trace-analysis).
+
+If `conventions.service_run` is not set → show:
+```
+⚠️  service_run is not configured in .agent/project-context.yaml.
+    Add it so this command can show the correct start command:
+
+    conventions:
+      service_run: "mvn spring-boot:run"   # or: npm run dev / go run . / etc.
+```
+Then ask the user to start the service manually and paste the error when ready.
+
+---
+
+### Path 3 — Test is failing
+
+Display the test command from `conventions.test_command` in `project-context.yaml`:
+
+```
+Run your tests first:
+
+  {conventions.test_command}
+
+Once the run finishes, paste the full test failure output here.
+
+Waiting...
+```
+
+Wait for the user to paste the failure output, then proceed to [Test Failure Analysis](#test-failure-analysis).
+
+If `conventions.test_command` is not set → show:
+```
+⚠️  test_command is not configured in .agent/project-context.yaml.
+    Add it so this command can show the correct test command:
+
+    conventions:
+      test_command: "mvn test"   # or: npm test / go test ./... / etc.
+```
+Then ask the user to run tests manually and paste the output when ready.
+
+---
+
+### Path 4 — Code question
+
+Ask:
+```
+Describe your question or paste the code snippet you're asking about:
+```
+
+Wait for input, then answer directly using loaded project context (architecture rules, layer order, coding standards from CLAUDE.md).
+
+---
 
 ## Stack Trace Analysis
+
 Read from **bottom up** — `Caused by:` is the real root cause:
 ```
 Caused by: {RealException}  ← start here
@@ -272,20 +392,83 @@ Caused by: {RealException}  ← start here
 
 ## Common Error Patterns
 
+Use `active_module` from context to select the relevant table.
+
+### If `platform_type = backend`
+
+#### java-spring / golang / dotnet / php-laravel
+
 | Error | Likely Cause | Fix Direction |
 |-------|-------------|---------------|
 | NullPointerException | Null object access; Optional not handled | Check Optional.orElseThrow, null guards |
 | ClassCastException | Wrong type assumption | Check type at assignment/return |
 | OutOfMemoryError | Loading too much data | Add pagination |
 | StackOverflowError | Infinite recursion | Find recursive call with no base case |
-| Connection refused | Dependency not running | Check config URLs |
+| Connection refused | Dependency not running | Check config URLs / start service |
 | 401 Unauthorized | Token expired, wrong config | Verify token, check auth config |
 | 403 Forbidden | Wrong role | Check auth annotations |
 | DB constraint violation | Duplicate key, null in NOT NULL | Check data and constraints |
 | Serialization error | Circular reference | Check DTO/mapper config |
 | Test assertion mismatch | Wrong mock or wrong expected | Re-read mock setup |
 
+#### context-engineering (AI/LLM pipelines)
+
+| Error | Likely Cause | Fix Direction |
+|-------|-------------|---------------|
+| `APIError` / `RateLimitError` | LLM quota exceeded or service down | Check API key, rate limits; add exponential backoff |
+| `TokenLimitError` / `context_length_exceeded` | Input prompt too long | Truncate/chunk input; review prompt template size |
+| `AuthenticationError` | API key invalid or expired | Check env var; rotate key |
+| Response validation / schema mismatch | LLM output doesn't match expected format | Add output parser; retry with stricter prompt |
+| `JSONDecodeError` on LLM output | Model returned non-JSON text | Add JSON extraction post-processing or stricter system prompt |
+| Hanging / slow test | Real LLM called in test instead of mock | Verify `patch('...')` applied; add timeout guard |
+| Flaky results across runs | Non-deterministic LLM response | Use fixed mock in tests; check temperature = 0 for determinism |
+
+### If `platform_type = web-frontend`
+
+| Error | Likely Cause | Fix Direction |
+|-------|-------------|---------------|
+| `Cannot read properties of undefined` | Data not loaded yet | Add loading guard / optional chaining `?.` |
+| `useEffect` infinite loop | Dependency array wrong | Review deps, use stable refs / `useCallback` |
+| `Cannot update state on unmounted component` | Async resolves after unmount | Cancel in cleanup / use AbortController |
+| CORS error | API not configured | Check backend CORS config or dev proxy setup |
+| 401 Unauthorized | Token expired or missing | Refresh token / check Authorization header |
+| White screen / no output | Unhandled render error | Check browser console, add ErrorBoundary |
+| Type error (Zod / TypeScript) | API response shape mismatch | Compare actual response vs type definition |
+| `act(...)` warning in test | Async state update | Wrap in `act(async () => {...})` |
+| Module not found | Import path wrong | Check relative path / tsconfig alias |
+
+### If `platform_type = mobile`
+
+#### Flutter
+| Error | Likely Cause | Fix Direction |
+|-------|-------------|---------------|
+| `Null check operator on null value` | Nullable not guarded | Add `?` or null check before `!` |
+| `pumpAndSettle timed out` | Async not completing in test | Use `pump(Duration(...))` |
+| `setState called after dispose` | Async continues after widget removed | Cancel in `dispose()` |
+| `RenderFlex overflow` | Widget too wide for screen | Wrap with `Flexible`, `Expanded`, or `SingleChildScrollView` |
+| BLoC state not updating | Event not dispatched | Verify `bloc.add(Event())` is called |
+| `MissingPluginException` | Native plugin not linked | Run `flutter clean && flutter pub get` |
+
+#### React Native
+| Error | Likely Cause | Fix Direction |
+|-------|-------------|---------------|
+| `undefined is not an object` | Null prop access | Add null check / optional chaining |
+| Metro bundler error | Cache stale | `npx react-native start --reset-cache` |
+| `VirtualizedLists nested` | FlatList inside ScrollView | Use `nestedScrollEnabled` or restructure |
+| Navigation `undefined` | `useNavigation` outside navigator | Wrap component inside correct navigator |
+| `act(...)` warning | Async state update in test | Wrap in `act(async () => {...})` |
+
+#### iOS / Android
+| Error | Likely Cause | Fix Direction |
+|-------|-------------|---------------|
+| `SIGABRT` / `EXC_BAD_ACCESS` (iOS) | Nil dereference | Add optional binding `if let` / `guard let` |
+| `IllegalStateException` (Android) | Lifecycle violation | Check if fragment/activity still attached |
+| `NetworkOnMainThreadException` | Network call on UI thread | Move to coroutine / background thread |
+| Build fails after pod install | Pod cache stale | `pod deintegrate && pod install` |
+| `Hilt injection failed` | Missing `@AndroidEntryPoint` | Add annotation to Activity/Fragment |
+
 ## Test Failure Analysis
+
 ```
 Expected: {value}
 Actual  : {value}
@@ -293,6 +476,8 @@ Actual  : {value}
 ```
 1. What is the gap? 2. Is mock setup correct? 3. Is assertion logically correct?
 
+---
+
 ## Output
 
 # Report Footer — Standard Command Output Format
@@ -323,6 +508,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}` |
@@ -331,13 +517,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          |
 

package/core/commands/define-product.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.
 
@@ -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}
@@ -269,6 +290,8 @@ AI scans the project and writes:
 | {original}       | {canonical}                          |
 ```
 
+Store this terminology map in the output product-definition file under a `## Terminology Map` section — `/generate-prd` will reference it during its Terminology Rules step to ensure consistency.
+
 ---
 
 ## Phase 1 — Feature Definition *(CHECKPOINT 1)*
@@ -305,7 +328,7 @@ Confirm → write `✅ PO Confirmed: Yes` → proceed.
 
 ---
 
-## Phase 3 — Clarification Log
+## Phase 3 — Clarification Log *(CHECKPOINT 3)*
 
 Based on Phases 1-2, AI identifies gaps and asks follow-up questions. Continue rounds until no Unresolved Items remain.
 
@@ -321,6 +344,8 @@ Based on Phases 1-2, AI identifies gaps and asks follow-up questions. Continue r
 ### Unresolved Items
 - {item — or "None"}
 
+When all Unresolved Items are resolved → write `✅ CHECKPOINT 3: No Unresolved Items` → proceed to Phase 4.
+
 ---
 
 ## Phase 4 — Business Rules *(CHECKPOINT 4)*
@@ -417,6 +442,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}` |
@@ -425,13 +451,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          |