@anhth2/spec-driven-dev-plugin 0.5.0

package/commands/debug.tmpl

@@ -0,0 +1,77 @@
+# /debug — Quick Debug Analysis
+
+Use for: IDE errors, test failures, strange behavior, or "why does this code do X?"
+Different from `/fix-bug`: analysis only, no full workflow, no ticket needed.
+
+## Gate
+{{include:steps/gate.md}}
+
+*Note: For this command, the target in Step 1 is user-provided input (stack trace, test failure output, file path + description, or code question). No file discovery needed — go straight to context loading.*
+
+## Context
+{{include:steps/context-loader.md}}
+
+---
+
+## 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
+
+## Stack Trace Analysis
+Read from **bottom up** — `Caused by:` is the real root cause:
+```
+Caused by: {RealException}  ← start here
+  at {class}.{method}({file}:{line})
+```
+
+## Common Error Patterns
+
+| 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 |
+| 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 |
+
+## Test Failure Analysis
+```
+Expected: {value}
+Actual  : {value}
+  at {test}.{method}(line {N})
+```
+1. What is the gap? 2. Is mock setup correct? 3. Is assertion logically correct?
+
+## Output
+
+{{include:steps/report-footer.md}}
+
+```
+/debug Analysis
+
+## Error
+{description}
+
+## Root Cause
+{technical explanation}
+
+## Location
+File: {path} | Line: {N} | Layer: {Controller/Service/Repository/Test}
+
+## Suggested Fix
+{specific code change}
+
+## Related Rule
+See CLAUDE.md §{section}
+
+## Next Step
+- To fully fix → /fix-bug {TICKET_ID}
+- Just needed analysis → done
+```

package/commands/define-product.md

@@ -0,0 +1,451 @@
+# /define-product — Feature Discovery (8-Phase Q&A)
+
+## Gate
+# Gate — Universal Entry Procedure
+
+Every command must execute this gate before proceeding with its specific logic.
+
+## Step 0 — Sub-Agent Mode Check
+
+Before anything else, check if `$ARGUMENTS` is a JSON payload from an orchestrator:
+
+1. Attempt to parse `$ARGUMENTS` as JSON.
+2. If it parses successfully **and** contains `"_agent_mode": true`:
+   - **Skip Steps 1, 2, and 3 of this Gate entirely.**
+   - Set target file = `payload.target_file`
+   - Set loaded context = `payload.context` (do NOT run context-loader.md)
+   - Set UC scope = `payload.uc_id` (process only this UC)
+   - Set line range = `payload.uc_section` (read only that PRD section)
+   - Proceed directly to the command-specific logic.
+3. If `$ARGUMENTS` is not JSON or `_agent_mode` is absent → continue to Step 1 (normal mode).
+
+## Step 0-B — Model Check
+
+*Skip this step if `_agent_mode: true` (sub-agent — orchestrator already validated).*
+
+Complex generation and review commands require strong reasoning.
+Using a smaller model risks missed edge cases, incomplete spec analysis, and architecture violations.
+
+Display and wait for response:
+
+```
+⚙️  MODEL CHECK
+──────────────────────────────────────────────────────────────────
+  Recommended  : claude-opus-4-5 (or claude-opus-4)
+  Why needed   : Spec analysis, architecture review, code generation
+                 require deep reasoning. Smaller models miss edge cases.
+
+  To switch in Claude Code:
+    • Settings → Model → select "claude-opus"
+    • or: /model → choose claude-opus
+
+  Running on claude-opus?
+    Y — yes, on claude-opus → proceed
+    S — skip check (I accept lower quality risk with current model)
+──────────────────────────────────────────────────────────────────
+```
+
+- "Y" → proceed to Step 1.
+- "S" → proceed to Step 1 (user accepts risk, add ⚠️ to final report).
+- "N" or anything else → **STOP.** Output: "Please switch to claude-opus, then re-run this command."
+
+## Step 1 — Resolve Target File
+
+1. If `$ARGUMENTS` is provided and points to an existing file → use it directly as the target.
+2. If `$ARGUMENTS` is a UC-ID, ticket ID, or partial name → search for matching files in the relevant directory.
+3. If `$ARGUMENTS` is empty or no match found:
+   - List files in the relevant directory for this command (e.g., `specs/prd/**/*.md` for PRD commands, `specs/bdd/**/*.feature` for BDD commands).
+   - Present the list to the user and ask: "Which file do you want to work with? (Enter number or filename)"
+   - Wait for user selection before continuing.
+
+## Step 2 — Execute Context Loader
+
+Load all project context by following the procedure in `steps/context-loader.md`.
+Store all loaded context in memory for use throughout this command session.
+
+## Step 3 — CHECKPOINT
+
+After completing Steps 1 and 2, display a summary and wait for confirmation:
+
+```
+CHECKPOINT
+-----------
+Target     : {resolved file path}
+Project    : {project.name from project-context.yaml}
+Tech stack : {language} / {framework}
+Module     : {module if set, else "not configured"}
+Domains    : {comma-separated domain list}
+
+Proceed? (Y/N)
+```
+
+Wait for explicit "Y" or "N" from the user before continuing.
+- "Y" → proceed to the command-specific steps below.
+- "N" → stop and ask what the user wants to change.
+
+
+*Note: For this command, there is no input file to resolve in Step 1. Skip to Step 2 (context load) and then ask: **"Ticket ID and feature name? (e.g., LOYAL-29 Loyalty Points)"***
+
+## Context
+# Context Loader — Load All Project Context
+
+Execute these steps in order. Store everything in memory for the duration of the command session.
+
+**Priority guide (anti-lost-in-middle):**
+- Steps 1–2 are PROJECT-CONFIG — loaded first, resolve all paths and metadata.
+- Step 3 is CRITICAL — architecture + coding standards, the highest-priority facts for generation.
+- Step 4 is SAFETY — data protection rules, enforced silently for the entire session.
+- Steps 5–6 are DOMAIN KNOWLEDGE — terminology and entity definitions.
+- Step 7 is the WORKING MEMORY RECAP — locks critical facts into the top of working memory.
+
+---
+
+## Step 1 — [PROJECT-CONFIG] Load project-context.yaml
+
+Read `.agent/project-context.yaml`. Extract and store:
+
+**Tech Stack:**
+- `tech_stack.language` → active language (e.g., Java 17, TypeScript, C#, Go)
+- `tech_stack.framework` → active framework (e.g., Spring Boot 3.2, Angular 17, .NET 8)
+- `tech_stack.build_tool` → build tool (e.g., Maven, npm, dotnet, go)
+- `tech_stack.test_framework` → test framework (e.g., JUnit 5 + Mockito, Jest, xUnit)
+- `tech_stack.database` → database (e.g., PostgreSQL, MySQL, MongoDB)
+- `tech_stack.module` → active module profile (e.g., java-spring, angular, dotnet, golang, context-engineering)
+
+**Conventions:**
+- `conventions.build_command` → how to compile/build
+- `conventions.test_command` → how to run tests
+- `conventions.service_run` → how to start the service
+- `conventions.ticket_prefix` → ticket ID prefix (e.g., PROJ, FEAT, UC)
+
+**Domains:**
+- `domains` → list of active business domains
+
+**Paths (if present):**
+- `paths.specs_dir` → BDD specs root
+- `paths.prd_dir` → PRD documents root
+- `paths.refinement_dir` → findings/review output dir
+- `paths.product_definitions_dir` → product definitions root
+- `paths.domain_knowledge_dir` → domain knowledge root
+- `paths.business_dictionary` → path to business-dictionary.md
+- `paths.core_entities` → path to core-entities.md
+- `paths.tech_docs_dir` → technical documentation root
+- `paths.trace_dir` → trace state directory
+
+If `paths` section is absent, use these defaults:
+- `specs_dir` = `specs/bdd`
+- `prd_dir` = `specs/prd`
+- `refinement_dir` = `.agent/review`
+- `product_definitions_dir` = `specs/product-definition`
+- `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`
+- `trace_dir` = `.trace`
+
+If `tech_stack.module` is set, also load `.agent/modules/{module}/stack-profile.yaml` if it exists.
+
+---
+
+## Step 2 — [PROJECT-CONFIG] Load module stack profile (conditional)
+
+If `tech_stack.module` is set, read `.agent/modules/{module}/stack-profile.yaml`.
+Merge framework-specific conventions (layer patterns, test patterns, naming rules) into the loaded context.
+If the file does not exist → skip silently.
+
+---
+
+## Step 3 — [CRITICAL] Load CLAUDE.md
+
+*This is the highest-priority context — it defines HOW to write code and documents for this project.*
+
+Read `CLAUDE.md`. Extract and store:
+
+- **§1 Project Overview** → project name, language, framework, build/test commands, domains
+- **§2 Architecture** → layer order (e.g., Controller → Facade → Service → Repository), architectural rules
+- **§3 Coding Standards** → naming conventions (classes, methods), response wrapper type, forbidden patterns
+- **§5 Error Handling** → exception types, HTTP status code mapping, not-found exception class name
+- **§7 Git Conventions** → branch naming pattern, commit message format
+
+If `CLAUDE.md` does not exist → note it as missing and continue with project-context.yaml data only.
+
+---
+
+## Step 4 — [SAFETY] Load Data Protection Rules
+
+Read `.agent/rules/data-protection.md` (or `rules/data-protection.md` from the framework installation).
+
+Store the sensitive file patterns — you must **never** read, write, display, or reference content from files matching those patterns for the entire session.
+
+If neither file exists → apply built-in defaults: never access `.env*`, `*.key`, `*.pem`, `*secret*`, `*password*`, `*credential*`.
+
+---
+
+## Step 5 — [DOMAIN] Load Business Dictionary (conditional)
+
+Check if the business dictionary file exists (use `paths.business_dictionary` resolved in Step 1).
+
+If it exists, read it and extract:
+- **Canonical Terms** → complete list of approved terms and their definitions
+- **Banned Terms** → complete list of banned terms and their canonical replacements
+- **Status / Enum Registry** → allowed enum values per entity
+
+Store the banned terms list for **active enforcement** throughout the command session:
+- When generating any text (PRD, BDD, code comments, tech docs), verify no banned terms appear
+- Replace banned terms with their canonical equivalents automatically
+
+If the file does not exist → skip silently. Do not warn or block.
+
+---
+
+## Step 6 — [DOMAIN] Load Core Entities (conditional)
+
+Check if the core entities file exists at `paths.core_entities` (resolved in Step 1).
+Default path: `specs/domain-knowledge/core-entities.md`.
+
+If it exists, read it and store:
+- **Entity catalog** → for each entity: its name, purpose, owner service, key fields (name + type), business invariants, and relationships
+- **Field name registry** → canonical field names to use in generated code and documents
+- **Relationship map** → how entities relate to each other (1:N, N:N, embedded, etc.)
+
+**How to use this catalog:**
+- When generating code: use the field names, types, and relationships defined here — do NOT infer from existing code
+- When generating PRD/BDD: reference entity names from this catalog for consistency
+- When generating tech-docs: use this catalog as the source-of-truth for entity definitions
+
+If the file does not exist → skip silently.
+
+---
+
+## Step 7 — [RECAP] Working Memory Recap (anti-lost-in-middle)
+
+After loading all context, synthesize and output a compact summary block.
+This recap ensures the most critical facts are stated at the END of context loading
+(recency effect — freshest in working memory when the task begins).
+
+Output exactly this block:
+```
+[CTX LOADED]
+Stack     : {language} / {framework} / {database}
+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}
+Status    : {FULL | PARTIAL — missing: CLAUDE.md / business-dict / core-entities | MINIMAL}
+```
+
+If any CRITICAL file is missing (CLAUDE.md), flag it clearly so the user can decide whether to proceed.
+
+---
+
+## Context Load Complete
+
+After completing all steps, you have loaded:
+- Project identity, tech stack, module conventions
+- Architecture rules and layer order  ← **[CRITICAL — hold in working memory]**
+- Coding standards and naming conventions  ← **[CRITICAL — hold in working memory]**
+- Data protection rules (sensitive file patterns to never access)
+- Terminology rules with banned-term list  ← **[DOMAIN — apply to every generated word]**
+- Entity catalog (field names, types, invariants)  ← **[DOMAIN — use for code generation]**
+- All configured paths
+
+Proceed to the next step of the calling command.
+
+
+---
+
+## Phase 0 — Knowledge Sync *(AI fills automatically, no PO input needed)*
+
+AI scans the project and writes:
+
+- **Related Entities** — list entities from existing PRDs/domain-knowledge that relate to this feature.
+- **Related Modules** — list affected modules/services.
+- **Existing Rules / Logic** — rules from existing PRDs that this feature must respect.
+- **Terminology Normalization** — map any terms found in PO input to canonical terms from business-dictionary.md.
+
+```
+| Term in PO input | Canonical term (business-dictionary) |
+|------------------|--------------------------------------|
+| {original}       | {canonical}                          |
+```
+
+---
+
+## Phase 1 — Feature Definition *(CHECKPOINT 1)*
+
+Ask in order, one at a time:
+
+1. **Context**: Background / reason why this feature is needed?
+2. **Problem**: Specific problem to solve?
+3. **Goal**: What objective does this feature achieve?
+4. **Actors**: Who are the users? (list roles, mark Primary/Secondary)
+5. **Scope**: What does this feature do? (one function per line — only what is in this ticket)
+6. **User Story**: Confirm in format:
+   ```
+   As a {User role}
+   I want to {User goal}
+   So that {Business value}
+   ```
+
+Summarize → confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 2 — User Flow Definition *(CHECKPOINT 2)*
+
+Ask:
+1. **Entry Point**: Where does the user start interacting with this feature?
+2. **Flow Steps**: Describe each step (use table):
+   ```
+   | Step | Action (user) | Screen / State | Notes |
+   ```
+3. **Exit Point**: What is the final result when the flow completes?
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 3 — Clarification Log
+
+Based on Phases 1-2, AI identifies gaps and asks follow-up questions. Continue rounds until no Unresolved Items remain.
+
+```
+### Round {N}
+| # | Category       | Question   | PO Answer  |
+|---|----------------|------------|------------|
+| 1 | Context/Flow/Logic | {question} | {answer} |
+```
+
+**BLOCK**: If Unresolved Items remain → MUST NOT proceed to Phase 4.
+
+### Unresolved Items
+- {item — or "None"}
+
+---
+
+## Phase 4 — Business Rules *(CHECKPOINT 4)*
+
+Derive from Phases 1-3. Each BR = one rule (WHAT the system must/must not do):
+
+```
+| Rule ID | Action / Trigger    | Rule                          | Condition           |
+|---------|---------------------|-------------------------------|---------------------|
+| BR-1    | {action from flow}  | System MUST/MUST NOT...       | {applicable condition} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 5 — Business Logic *(CHECKPOINT 5)*
+
+Map each BR to HOW the system executes it:
+
+```
+| Rule ID | System Behavior                       | Data State Change   | UI Behavior             | Error Handling         |
+|---------|---------------------------------------|---------------------|-------------------------|------------------------|
+| BR-1    | {how system processes when triggers}  | {what data changes} | {enable/disable/show...}| {error message/action} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 6 — Acceptance Criteria *(CHECKPOINT 6)*
+
+Derive from BRs + User Story. Each AC must be testable (clear pass/fail):
+
+```
+| AC ID | Description             | Expected Behavior         | Derived from |
+|-------|-------------------------|---------------------------|--------------|
+| AC-1  | {criterion description} | {what system should do}   | BR-{N}       |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 7 — Validation Report
+
+Generate coverage matrix automatically:
+
+```
+| Flow Action | Has Rule? | Has Logic? | Has AC? | Status  |
+|-------------|-----------|------------|---------|---------|
+| {Action 1}  | ✅/❌     | ✅/❌      | ✅/❌   | OK/GAP  |
+```
+
+- **Conflicts Detected**: list any conflicting rules, or "None".
+- **Missing Items**: list gaps, or "None".
+
+If any GAP found → alert PO and resolve before marking completed.
+
+---
+
+## Output
+
+Write `{paths.product_definitions_dir}/{TICKET-ID}-{slug}.md` following `templates/product-definition.template.md`.
+
+Fill all sections with data gathered across phases.
+Set `Status: completed` when Phase 7 passes with no GAPs.
+
+# 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                                  |
+|-------------------------|-----------------------------------------------|
+| /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          | `/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             |
+| /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}
+```
+
+
+```
+/define-product Complete ✅
+File: {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+Next: /generate-prd {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+```

package/commands/define-product.tmpl

@@ -0,0 +1,154 @@
+# /define-product — Feature Discovery (8-Phase Q&A)
+
+## Gate
+{{include:steps/gate.md}}
+
+*Note: For this command, there is no input file to resolve in Step 1. Skip to Step 2 (context load) and then ask: **"Ticket ID and feature name? (e.g., LOYAL-29 Loyalty Points)"***
+
+## Context
+{{include:steps/context-loader.md}}
+
+---
+
+## Phase 0 — Knowledge Sync *(AI fills automatically, no PO input needed)*
+
+AI scans the project and writes:
+
+- **Related Entities** — list entities from existing PRDs/domain-knowledge that relate to this feature.
+- **Related Modules** — list affected modules/services.
+- **Existing Rules / Logic** — rules from existing PRDs that this feature must respect.
+- **Terminology Normalization** — map any terms found in PO input to canonical terms from business-dictionary.md.
+
+```
+| Term in PO input | Canonical term (business-dictionary) |
+|------------------|--------------------------------------|
+| {original}       | {canonical}                          |
+```
+
+---
+
+## Phase 1 — Feature Definition *(CHECKPOINT 1)*
+
+Ask in order, one at a time:
+
+1. **Context**: Background / reason why this feature is needed?
+2. **Problem**: Specific problem to solve?
+3. **Goal**: What objective does this feature achieve?
+4. **Actors**: Who are the users? (list roles, mark Primary/Secondary)
+5. **Scope**: What does this feature do? (one function per line — only what is in this ticket)
+6. **User Story**: Confirm in format:
+   ```
+   As a {User role}
+   I want to {User goal}
+   So that {Business value}
+   ```
+
+Summarize → confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 2 — User Flow Definition *(CHECKPOINT 2)*
+
+Ask:
+1. **Entry Point**: Where does the user start interacting with this feature?
+2. **Flow Steps**: Describe each step (use table):
+   ```
+   | Step | Action (user) | Screen / State | Notes |
+   ```
+3. **Exit Point**: What is the final result when the flow completes?
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 3 — Clarification Log
+
+Based on Phases 1-2, AI identifies gaps and asks follow-up questions. Continue rounds until no Unresolved Items remain.
+
+```
+### Round {N}
+| # | Category       | Question   | PO Answer  |
+|---|----------------|------------|------------|
+| 1 | Context/Flow/Logic | {question} | {answer} |
+```
+
+**BLOCK**: If Unresolved Items remain → MUST NOT proceed to Phase 4.
+
+### Unresolved Items
+- {item — or "None"}
+
+---
+
+## Phase 4 — Business Rules *(CHECKPOINT 4)*
+
+Derive from Phases 1-3. Each BR = one rule (WHAT the system must/must not do):
+
+```
+| Rule ID | Action / Trigger    | Rule                          | Condition           |
+|---------|---------------------|-------------------------------|---------------------|
+| BR-1    | {action from flow}  | System MUST/MUST NOT...       | {applicable condition} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 5 — Business Logic *(CHECKPOINT 5)*
+
+Map each BR to HOW the system executes it:
+
+```
+| Rule ID | System Behavior                       | Data State Change   | UI Behavior             | Error Handling         |
+|---------|---------------------------------------|---------------------|-------------------------|------------------------|
+| BR-1    | {how system processes when triggers}  | {what data changes} | {enable/disable/show...}| {error message/action} |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 6 — Acceptance Criteria *(CHECKPOINT 6)*
+
+Derive from BRs + User Story. Each AC must be testable (clear pass/fail):
+
+```
+| AC ID | Description             | Expected Behavior         | Derived from |
+|-------|-------------------------|---------------------------|--------------|
+| AC-1  | {criterion description} | {what system should do}   | BR-{N}       |
+```
+
+Confirm → write `✅ PO Confirmed: Yes` → proceed.
+
+---
+
+## Phase 7 — Validation Report
+
+Generate coverage matrix automatically:
+
+```
+| Flow Action | Has Rule? | Has Logic? | Has AC? | Status  |
+|-------------|-----------|------------|---------|---------|
+| {Action 1}  | ✅/❌     | ✅/❌      | ✅/❌   | OK/GAP  |
+```
+
+- **Conflicts Detected**: list any conflicting rules, or "None".
+- **Missing Items**: list gaps, or "None".
+
+If any GAP found → alert PO and resolve before marking completed.
+
+---
+
+## Output
+
+Write `{paths.product_definitions_dir}/{TICKET-ID}-{slug}.md` following `templates/product-definition.template.md`.
+
+Fill all sections with data gathered across phases.
+Set `Status: completed` when Phase 7 passes with no GAPs.
+
+{{include:steps/report-footer.md}}
+
+```
+/define-product Complete ✅
+File: {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+Next: /generate-prd {paths.product_definitions_dir}/{TICKET-ID}-{slug}.md
+```