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

package/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/commands/run-tests.tmpl

@@ -3,44 +3,164 @@
 ## Gate
 {{include:steps/gate.md}}
 
-*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
 {{include:steps/context-loader.md}}
 
 ---
 
+## 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 |
 |---|---|---|
-| 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 |
+| `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 |
+|---|---|---|
+| `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
 
 {{include:steps/report-footer.md}}
 
 ```
-/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/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.
 
@@ -86,15 +86,17 @@ 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, 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
 
@@ -106,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/
@@ -151,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}
 
@@ -171,7 +173,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."
 
@@ -254,9 +256,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
@@ -266,6 +284,62 @@ Instruct: "Open `specs/domain-knowledge/core-entities.md` and define your key do
 
 ## 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:
@@ -274,5 +348,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
 ```