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

package/commands/setup-ai-first.tmpl

@@ -5,15 +5,17 @@ Walk the user through a one-time setup that creates all required directories, in
 ## Gate
 {{include:steps/gate.md}}
 
-*Note: For this command, there is no input file. Skip Step 1 file discovery. In Step 2, skip project-context.yaml loading (it does not exist yet). Ask: "Which project are you setting up? Give me the root path of the project."*
+*Note: For this command — **skip Gate Steps 1, 2, and 3** (there is no input file and no project context yet). Only run Step 0-B (model check). The project root is the **current working directory**. Proceed directly to the Precondition Check below.*
 
 ---
 
 ## Precondition Check
 
 Check if already set up:
-- If `.claude/commands/` exists with `.md` files → report "Already set up."
-- If `specs/` exists → offer to re-initialize or skip
+- If `CLAUDE.md` **and** `.agent/project-context.yaml` both exist → ask: "This project is already initialized. Re-run setup to regenerate config files? (Y/N)"
+  - N → stop
+  - 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 1 — Create Directory Structure
 
@@ -25,8 +27,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/
@@ -70,7 +72,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}
 
@@ -90,7 +92,7 @@ commit_feature: "feat({{TICKET_PREFIX}}-{N}): {description}"
 
 ## Step 3 — Create project-context.yaml
 
-Create `.agent/project-context.yaml` using `templates/project-context.yaml` as the source template.
+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."
 
@@ -173,9 +175,25 @@ Create `specs/domain-knowledge/core-entities.md` if it does not exist:
 
 Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key domain entities. Start with aggregate roots. This file is loaded by every AI command — good definitions here save significant back-and-forth during code generation."
 
-## Step 6 — Verify
+## Step 6 — Install VS Code Extension (Recommended)
+
+Recommend the user install the **Spec Driven Dev** VS Code extension — it provides Review Board + Living Documentation panels that integrate with this workflow.
+
+```bash
+code --install-extension edupia-team.spec-driven-dev-team
+```
+
+Or: VS Code → `Ctrl+Shift+P` → **"Extensions: Install from Marketplace"** → search **Spec Driven Dev**.
+
+**What it does:**
+- 📋 **Review Board** — visual UI to review findings from `/refine-prd`, `/review-context`, `/review-tech-docs`
+- 📊 **Living Documentation** — traceability dashboard driven by `.trace/*.tsv`
+
+## Step 7 — Verify
 
 - [ ] `specs/` exists
+- [ ] `specs/bdd/` exists
+- [ ] `specs/tech-docs/` exists
 - [ ] `specs/domain-knowledge/` exists
 - [ ] `.trace/` exists
 - [ ] `.agent/project-context.yaml` exists
@@ -185,6 +203,8 @@ Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key do
 
 ## Output
 
+{{include:steps/report-footer.md}}
+
 ```
 /setup-ai-first Complete ✅
 Next:
@@ -193,5 +213,7 @@ Next:
   3. Fill specs/domain-knowledge/business-dictionary.md  ← terminology rules
   4. Fill specs/domain-knowledge/core-entities.md        ← entity glossary for code gen
   5. git add and commit those 4 files
-  6. /define-product to start your first feature
+  6. Install VS Code extension (if not yet installed):
+     code --install-extension edupia-team.spec-driven-dev-team
+  7. /define-product to start your first feature
 ```

package/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
 ```

package/commands/smoke-test.tmpl

@@ -1,30 +1,51 @@
-# /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
 {{include:steps/gate.md}}
 
-*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
 {{include:steps/context-loader.md}}
 
 ---
 
-## 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)
@@ -32,10 +53,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
@@ -45,7 +67,6 @@ curl -s -X POST "http://localhost:{port}/v1/{resource}" \
   -d '{"field1": "test_value"}'
 ```
 
-## Interpret Results
 | Result | Meaning |
 |--------|---------|
 | 200/201 + correct data | ✅ OK |
@@ -53,17 +74,144 @@ 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
 
 {{include:steps/report-footer.md}}
 
 ```
 /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
 ```