@anhth2/spec-driven-dev-plugin 0.9.0 → 0.9.1

package/commands/generate-prd.md

@@ -450,13 +450,14 @@ Write `{paths.prd_dir}/{domain}/{TICKET-ID}-{slug}.md` using the structure below
 
 ## a. User Story
 
-As a {User role}
-I want to {User goal}
-So that {Business value}
+- **As a** {User role}
+- **I want to** {User goal}
+- **So that** {Business value}
 
 ## b. Scope
 
-In Scope
+**In Scope**
+
 - {Function 1}
 - {Function 2}
 
@@ -464,24 +465,36 @@ In Scope
 
 # 2. Acceptance Criteria
 
-AC1: {Acceptance criterion — testable, observable, no UI details}
-AC2: {Acceptance criterion}
+- **AC1:** {Acceptance criterion — testable, observable, no UI details}
+- **AC2:** {Acceptance criterion}
 
 ---
 
 # 3. Use Case
 
 #### {TICKET-ID}-UC1: {Use Case Name}
-Actor: {User performing the action}
-Description: {Business scenario description — 1 sentence}
-Pre-condition: {Condition that must be true BEFORE use case begins}
-Post-condition: {State / result AFTER use case completes}
 
-Business Rule
-| ID                      | Business Rule                        | Business Logic                            |
-|-------------------------|--------------------------------------|-------------------------------------------|
-| {TICKET-ID}-UC1-BR1     | {Rule — WHAT the system must do}    | - Logic 1<br/>- Logic 2<br/>- Logic 3    |
-| {TICKET-ID}-UC1-BR2     | {Rule}                               | - Logic                                  |
+- **Actor:** {User performing the action}
+- **Description:** {Business scenario description — 1 sentence}
+- **Pre-condition:** {Condition that must be true BEFORE use case begins}
+- **Post-condition:** {State / result AFTER use case completes}
+
+**Business Rule**
+
+| ID | Business Rule |
+|----|---------------|
+| {TICKET-ID}-UC1-BR1 | {Rule — WHAT the system must do} |
+| {TICKET-ID}-UC1-BR2 | {Rule} |
+
+**Business Logic**
+
+**{TICKET-ID}-UC1-BR1:**
+- Logic 1
+- Logic 2
+- Logic 3
+
+**{TICKET-ID}-UC1-BR2:**
+- Logic
 
 ---
 
@@ -503,11 +516,16 @@ flowchart TD
 
 **Screen 1: {Screen Name}**
 
-| Component      | Details                                                         |
-|----------------|-----------------------------------------------------------------|
-| **Screen**     | {Screen name}                                                   |
-| **Components** | - {Component 1}<br/>- {Component 2}<br/>- {Component 3}        |
-| **Actions**    | - {Action 1} → {Result}<br/>- {Action 2} → {Result}           |
+**Screen:** {Screen name}
+
+**Components:**
+- {Component 1}
+- {Component 2}
+- {Component 3}
+
+**Actions:**
+- {Action 1} → {Result}
+- {Action 2} → {Result}
 
 ---
 
@@ -557,6 +575,7 @@ flowchart TD
 - [ ] No banned terms (if dictionary exists)
 - [ ] User Flow includes error path / exception path
 - [ ] Wireframe covers all screens related to Use Cases
+- [ ] **Định dạng (readability)**: User Story / AC / các field của UC (Actor, Description, Pre/Post-condition) viết dạng bullet `- **Label:** …` — mỗi ý MỘT dòng, KHÔNG viết các dòng liền nhau (sẽ bị dồn thành 1 đoạn khi render); có một dòng trống trước và sau mỗi bảng
 
 ## Changelog Section (append at end of PRD)
 

package/commands/generate-prd.tmpl

@@ -98,13 +98,14 @@ Write `{paths.prd_dir}/{domain}/{TICKET-ID}-{slug}.md` using the structure below
 
 ## a. User Story
 
-As a {User role}
-I want to {User goal}
-So that {Business value}
+- **As a** {User role}
+- **I want to** {User goal}
+- **So that** {Business value}
 
 ## b. Scope
 
-In Scope
+**In Scope**
+
 - {Function 1}
 - {Function 2}
 
@@ -112,24 +113,36 @@ In Scope
 
 # 2. Acceptance Criteria
 
-AC1: {Acceptance criterion — testable, observable, no UI details}
-AC2: {Acceptance criterion}
+- **AC1:** {Acceptance criterion — testable, observable, no UI details}
+- **AC2:** {Acceptance criterion}
 
 ---
 
 # 3. Use Case
 
 #### {TICKET-ID}-UC1: {Use Case Name}
-Actor: {User performing the action}
-Description: {Business scenario description — 1 sentence}
-Pre-condition: {Condition that must be true BEFORE use case begins}
-Post-condition: {State / result AFTER use case completes}
 
-Business Rule
-| ID                      | Business Rule                        | Business Logic                            |
-|-------------------------|--------------------------------------|-------------------------------------------|
-| {TICKET-ID}-UC1-BR1     | {Rule — WHAT the system must do}    | - Logic 1<br/>- Logic 2<br/>- Logic 3    |
-| {TICKET-ID}-UC1-BR2     | {Rule}                               | - Logic                                  |
+- **Actor:** {User performing the action}
+- **Description:** {Business scenario description — 1 sentence}
+- **Pre-condition:** {Condition that must be true BEFORE use case begins}
+- **Post-condition:** {State / result AFTER use case completes}
+
+**Business Rule**
+
+| ID | Business Rule |
+|----|---------------|
+| {TICKET-ID}-UC1-BR1 | {Rule — WHAT the system must do} |
+| {TICKET-ID}-UC1-BR2 | {Rule} |
+
+**Business Logic**
+
+**{TICKET-ID}-UC1-BR1:**
+- Logic 1
+- Logic 2
+- Logic 3
+
+**{TICKET-ID}-UC1-BR2:**
+- Logic
 
 ---
 
@@ -151,11 +164,16 @@ flowchart TD
 
 **Screen 1: {Screen Name}**
 
-| Component      | Details                                                         |
-|----------------|-----------------------------------------------------------------|
-| **Screen**     | {Screen name}                                                   |
-| **Components** | - {Component 1}<br/>- {Component 2}<br/>- {Component 3}        |
-| **Actions**    | - {Action 1} → {Result}<br/>- {Action 2} → {Result}           |
+**Screen:** {Screen name}
+
+**Components:**
+- {Component 1}
+- {Component 2}
+- {Component 3}
+
+**Actions:**
+- {Action 1} → {Result}
+- {Action 2} → {Result}
 
 ---
 
@@ -205,6 +223,7 @@ flowchart TD
 - [ ] No banned terms (if dictionary exists)
 - [ ] User Flow includes error path / exception path
 - [ ] Wireframe covers all screens related to Use Cases
+- [ ] **Định dạng (readability)**: User Story / AC / các field của UC (Actor, Description, Pre/Post-condition) viết dạng bullet `- **Label:** …` — mỗi ý MỘT dòng, KHÔNG viết các dòng liền nhau (sẽ bị dồn thành 1 đoạn khi render); có một dòng trống trước và sau mỗi bảng
 
 ## Changelog Section (append at end of PRD)
 

package/commands/refine-prd.md

@@ -389,7 +389,9 @@ findings:
   - id: "F001"
     lens: "QA"           # QA | DEV | SA | PO
     severity: "major"    # critical | major | minor
-    section: "§6. Acceptance Criteria"
+    section: "§6. Acceptance Criteria"   # human-readable heading/section label
+    uc_id: "{TICKET-ID}-UC{N}"           # UC this finding belongs to; "" if PRD-global (scope, metrics, problem statement)
+    quote: "{verbatim snippet copied EXACTLY from the PRD at the issue location, ≤120 chars}"
     finding: "{description of gap or issue}"
     suggestion: "{specific actionable improvement}"
     auto_fixable: false  # true = AI applies in --resume; false = human must write decision in note
@@ -402,6 +404,12 @@ summary:
   recommendation: "APPROVED_WITH_MINOR_CHANGES | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the PRD at the exact spot the
+> issue occurs — do NOT paraphrase; it is matched against the document to locate the line. Set
+> `uc_id` to the owning Use Case (or `""` for PRD-global findings). These let a reviewer click a
+> finding in the Review Board and jump straight to the precise location in the source PRD.
+
 ## Report
 
 # Report Footer — Standard Command Output Format

package/commands/refine-prd.tmpl

@@ -37,7 +37,9 @@ findings:
   - id: "F001"
     lens: "QA"           # QA | DEV | SA | PO
     severity: "major"    # critical | major | minor
-    section: "§6. Acceptance Criteria"
+    section: "§6. Acceptance Criteria"   # human-readable heading/section label
+    uc_id: "{TICKET-ID}-UC{N}"           # UC this finding belongs to; "" if PRD-global (scope, metrics, problem statement)
+    quote: "{verbatim snippet copied EXACTLY from the PRD at the issue location, ≤120 chars}"
     finding: "{description of gap or issue}"
     suggestion: "{specific actionable improvement}"
     auto_fixable: false  # true = AI applies in --resume; false = human must write decision in note
@@ -50,6 +52,12 @@ summary:
   recommendation: "APPROVED_WITH_MINOR_CHANGES | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the PRD at the exact spot the
+> issue occurs — do NOT paraphrase; it is matched against the document to locate the line. Set
+> `uc_id` to the owning Use Case (or `""` for PRD-global findings). These let a reviewer click a
+> finding in the Review Board and jump straight to the precise location in the source PRD.
+
 ## Report
 
 {{include:steps/report-footer.md}}

package/commands/review-context.md

@@ -563,6 +563,8 @@ findings:
     check_id: "P1"           # P1-P5 for PRD; B1-B6 for BDD
     severity: "critical"     # critical | major | minor
     section: "{section or scenario ID where issue was found}"
+    uc_id: "{UC-ID this finding belongs to — PRD: the UC heading; BDD: @trace.id; \"\" if global}"
+    quote: "{verbatim snippet copied EXACTLY from the reviewed file at the issue location, ≤120 chars}"
     finding: "{clear description of the issue}"
     suggestion: "{specific actionable fix — AI will apply this in --resume if accepted}"
     auto_fixable: true       # true = AI can apply; false = human must write note in Review Board
@@ -576,6 +578,12 @@ summary:
   recommendation: "APPROVED | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the reviewed file at the exact
+> spot the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> Set `uc_id` to the owning Use Case (`@trace.id` for BDD, the UC heading for PRD; `""` if global).
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Post-Analysis Routing
 
 After running all checks and writing the findings file:

package/commands/review-context.tmpl

@@ -211,6 +211,8 @@ findings:
     check_id: "P1"           # P1-P5 for PRD; B1-B6 for BDD
     severity: "critical"     # critical | major | minor
     section: "{section or scenario ID where issue was found}"
+    uc_id: "{UC-ID this finding belongs to — PRD: the UC heading; BDD: @trace.id; \"\" if global}"
+    quote: "{verbatim snippet copied EXACTLY from the reviewed file at the issue location, ≤120 chars}"
     finding: "{clear description of the issue}"
     suggestion: "{specific actionable fix — AI will apply this in --resume if accepted}"
     auto_fixable: true       # true = AI can apply; false = human must write note in Review Board
@@ -224,6 +226,12 @@ summary:
   recommendation: "APPROVED | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the reviewed file at the exact
+> spot the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> Set `uc_id` to the owning Use Case (`@trace.id` for BDD, the UC heading for PRD; `""` if global).
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Post-Analysis Routing
 
 After running all checks and writing the findings file:

package/commands/review-tech-docs.md

@@ -554,6 +554,8 @@ findings:
     check_id: "T1"           # T1–T7
     severity: "critical"     # critical | major | minor
     section: "{section heading or component name where issue was found}"
+    uc_id: "{UC-ID}"         # same as top-level uc_id (the UC this tech-doc designs)
+    quote: "{verbatim snippet copied EXACTLY from the tech-doc at the issue location, ≤120 chars}"
     finding: "{clear description of the violation or gap}"
     suggestion: "{specific fix — AI applies this in --resume if accepted}"
     auto_fixable: false      # true = AI can apply; false = human must write decision in note
@@ -568,6 +570,11 @@ summary:
   sign_off_gate: "{blocked — pending: fe_team, app_team, sa | ready}"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the tech-doc at the exact spot
+> the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Report
 
 # Report Footer — Standard Command Output Format

package/commands/review-tech-docs.tmpl

@@ -202,6 +202,8 @@ findings:
     check_id: "T1"           # T1–T7
     severity: "critical"     # critical | major | minor
     section: "{section heading or component name where issue was found}"
+    uc_id: "{UC-ID}"         # same as top-level uc_id (the UC this tech-doc designs)
+    quote: "{verbatim snippet copied EXACTLY from the tech-doc at the issue location, ≤120 chars}"
     finding: "{clear description of the violation or gap}"
     suggestion: "{specific fix — AI applies this in --resume if accepted}"
     auto_fixable: false      # true = AI can apply; false = human must write decision in note
@@ -216,6 +218,11 @@ summary:
   sign_off_gate: "{blocked — pending: fe_team, app_team, sa | ready}"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the tech-doc at the exact spot
+> the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Report
 
 {{include:steps/report-footer.md}}

package/core/FRAMEWORK_VERSION

@@ -1 +1 @@
-0.9.0
+0.9.1

package/core/commands/generate-prd.md

@@ -450,13 +450,14 @@ Write `{paths.prd_dir}/{domain}/{TICKET-ID}-{slug}.md` using the structure below
 
 ## a. User Story
 
-As a {User role}
-I want to {User goal}
-So that {Business value}
+- **As a** {User role}
+- **I want to** {User goal}
+- **So that** {Business value}
 
 ## b. Scope
 
-In Scope
+**In Scope**
+
 - {Function 1}
 - {Function 2}
 
@@ -464,24 +465,36 @@ In Scope
 
 # 2. Acceptance Criteria
 
-AC1: {Acceptance criterion — testable, observable, no UI details}
-AC2: {Acceptance criterion}
+- **AC1:** {Acceptance criterion — testable, observable, no UI details}
+- **AC2:** {Acceptance criterion}
 
 ---
 
 # 3. Use Case
 
 #### {TICKET-ID}-UC1: {Use Case Name}
-Actor: {User performing the action}
-Description: {Business scenario description — 1 sentence}
-Pre-condition: {Condition that must be true BEFORE use case begins}
-Post-condition: {State / result AFTER use case completes}
 
-Business Rule
-| ID                      | Business Rule                        | Business Logic                            |
-|-------------------------|--------------------------------------|-------------------------------------------|
-| {TICKET-ID}-UC1-BR1     | {Rule — WHAT the system must do}    | - Logic 1<br/>- Logic 2<br/>- Logic 3    |
-| {TICKET-ID}-UC1-BR2     | {Rule}                               | - Logic                                  |
+- **Actor:** {User performing the action}
+- **Description:** {Business scenario description — 1 sentence}
+- **Pre-condition:** {Condition that must be true BEFORE use case begins}
+- **Post-condition:** {State / result AFTER use case completes}
+
+**Business Rule**
+
+| ID | Business Rule |
+|----|---------------|
+| {TICKET-ID}-UC1-BR1 | {Rule — WHAT the system must do} |
+| {TICKET-ID}-UC1-BR2 | {Rule} |
+
+**Business Logic**
+
+**{TICKET-ID}-UC1-BR1:**
+- Logic 1
+- Logic 2
+- Logic 3
+
+**{TICKET-ID}-UC1-BR2:**
+- Logic
 
 ---
 
@@ -503,11 +516,16 @@ flowchart TD
 
 **Screen 1: {Screen Name}**
 
-| Component      | Details                                                         |
-|----------------|-----------------------------------------------------------------|
-| **Screen**     | {Screen name}                                                   |
-| **Components** | - {Component 1}<br/>- {Component 2}<br/>- {Component 3}        |
-| **Actions**    | - {Action 1} → {Result}<br/>- {Action 2} → {Result}           |
+**Screen:** {Screen name}
+
+**Components:**
+- {Component 1}
+- {Component 2}
+- {Component 3}
+
+**Actions:**
+- {Action 1} → {Result}
+- {Action 2} → {Result}
 
 ---
 
@@ -557,6 +575,7 @@ flowchart TD
 - [ ] No banned terms (if dictionary exists)
 - [ ] User Flow includes error path / exception path
 - [ ] Wireframe covers all screens related to Use Cases
+- [ ] **Định dạng (readability)**: User Story / AC / các field của UC (Actor, Description, Pre/Post-condition) viết dạng bullet `- **Label:** …` — mỗi ý MỘT dòng, KHÔNG viết các dòng liền nhau (sẽ bị dồn thành 1 đoạn khi render); có một dòng trống trước và sau mỗi bảng
 
 ## Changelog Section (append at end of PRD)
 

package/core/commands/refine-prd.md

@@ -389,7 +389,9 @@ findings:
   - id: "F001"
     lens: "QA"           # QA | DEV | SA | PO
     severity: "major"    # critical | major | minor
-    section: "§6. Acceptance Criteria"
+    section: "§6. Acceptance Criteria"   # human-readable heading/section label
+    uc_id: "{TICKET-ID}-UC{N}"           # UC this finding belongs to; "" if PRD-global (scope, metrics, problem statement)
+    quote: "{verbatim snippet copied EXACTLY from the PRD at the issue location, ≤120 chars}"
     finding: "{description of gap or issue}"
     suggestion: "{specific actionable improvement}"
     auto_fixable: false  # true = AI applies in --resume; false = human must write decision in note
@@ -402,6 +404,12 @@ summary:
   recommendation: "APPROVED_WITH_MINOR_CHANGES | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the PRD at the exact spot the
+> issue occurs — do NOT paraphrase; it is matched against the document to locate the line. Set
+> `uc_id` to the owning Use Case (or `""` for PRD-global findings). These let a reviewer click a
+> finding in the Review Board and jump straight to the precise location in the source PRD.
+
 ## Report
 
 # Report Footer — Standard Command Output Format

package/core/commands/review-context.md

@@ -563,6 +563,8 @@ findings:
     check_id: "P1"           # P1-P5 for PRD; B1-B6 for BDD
     severity: "critical"     # critical | major | minor
     section: "{section or scenario ID where issue was found}"
+    uc_id: "{UC-ID this finding belongs to — PRD: the UC heading; BDD: @trace.id; \"\" if global}"
+    quote: "{verbatim snippet copied EXACTLY from the reviewed file at the issue location, ≤120 chars}"
     finding: "{clear description of the issue}"
     suggestion: "{specific actionable fix — AI will apply this in --resume if accepted}"
     auto_fixable: true       # true = AI can apply; false = human must write note in Review Board
@@ -576,6 +578,12 @@ summary:
   recommendation: "APPROVED | NEEDS_REVISION | BLOCKED"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the reviewed file at the exact
+> spot the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> Set `uc_id` to the owning Use Case (`@trace.id` for BDD, the UC heading for PRD; `""` if global).
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Post-Analysis Routing
 
 After running all checks and writing the findings file:

package/core/commands/review-tech-docs.md

@@ -554,6 +554,8 @@ findings:
     check_id: "T1"           # T1–T7
     severity: "critical"     # critical | major | minor
     section: "{section heading or component name where issue was found}"
+    uc_id: "{UC-ID}"         # same as top-level uc_id (the UC this tech-doc designs)
+    quote: "{verbatim snippet copied EXACTLY from the tech-doc at the issue location, ≤120 chars}"
     finding: "{clear description of the violation or gap}"
     suggestion: "{specific fix — AI applies this in --resume if accepted}"
     auto_fixable: false      # true = AI can apply; false = human must write decision in note
@@ -568,6 +570,11 @@ summary:
   sign_off_gate: "{blocked — pending: fe_team, app_team, sa | ready}"
 ```
 
+> **Locator fields (`quote` + `uc_id`) — required for Review Board source-jump.**
+> For every finding, copy a short **verbatim** `quote` straight from the tech-doc at the exact spot
+> the issue occurs — do NOT paraphrase; it is matched against the document to locate the line.
+> These let a reviewer click a finding in the Review Board and jump to the precise source location.
+
 ## Report
 
 # Report Footer — Standard Command Output Format

package/core/templates/prd.template.md

@@ -102,9 +102,9 @@
   - {Business value}→ Giá trị nghiệp vụ mang lại (lý do tại sao người dùng cần điều này)
 -->
 
-As a {User role}
-I want to {User goal}
-So that {Business value}
+- **As a** {User role}
+- **I want to** {User goal}
+- **So that** {Business value}
 
 ## b. Phạm vi
 
@@ -119,7 +119,8 @@ So that {Business value}
   - Viết ngắn gọn, súc tích, đủ để người đọc hiểu mà không cần giải thích thêm.
 -->
 
-In Scope
+**In Scope**
+
 - {Chức năng thuộc feature}
 
 ---
@@ -141,9 +142,9 @@ In Scope
   - Chi tiết kỹ thuật hoặc logic xử lý nội bộ → thuộc Business Rule / Business Logic.
 -->
 
-AC1: {Điều kiện chấp nhận}
-AC2: {Điều kiện chấp nhận}
-AC3: {Điều kiện chấp nhận}
+- **AC1:** {Điều kiện chấp nhận}
+- **AC2:** {Điều kiện chấp nhận}
+- **AC3:** {Điều kiện chấp nhận}
 
 ---
 
@@ -183,15 +184,24 @@ AC3: {Điều kiện chấp nhận}
 -->
 
 #### {TICKET_ID}-UC1: {Tên Use Case}
-Actor: {Người dùng thực hiện}
-Description: {Mô tả ngắn gọn kịch bản nghiệp vụ}
-Pre-condition: {Điều kiện cần trước khi Use Case bắt đầu}
-Post-condition: {Kết quả sau khi Use Case hoàn thành}
 
-Business Rule
-| ID | Business Rule | Business Logic |
-|----|---------------|----------------|
-| {TICKET_ID}-UC1-BR1 |               | - Logic 1<br/>- Logic 2<br/>- Logic 3 |
+- **Actor:** {Người dùng thực hiện}
+- **Description:** {Mô tả ngắn gọn kịch bản nghiệp vụ}
+- **Pre-condition:** {Điều kiện cần trước khi Use Case bắt đầu}
+- **Post-condition:** {Kết quả sau khi Use Case hoàn thành}
+
+**Business Rule**
+
+| ID | Business Rule |
+|----|---------------|
+| {TICKET_ID}-UC1-BR1 | |
+
+**Business Logic**
+
+**{TICKET_ID}-UC1-BR1:**
+- Logic 1
+- Logic 2
+- Logic 3
 
 ---
 
@@ -246,11 +256,16 @@ flowchart TD
 
 **Screen N: {Tên màn hình}**
 
-| Thành phần     | Chi tiết |
-| -------------- | -------- |
-| **Screen**     | {Tên màn hình} |
-| **Components** | - {Component 1} <br>- {Component 2} <br>- {Component 3} |
-| **Actions**    | - {Hành động 1} → {Kết quả} <br>- {Hành động 2} → {Kết quả} |
+**Screen:** {Tên màn hình}
+
+**Components:**
+- {Component 1}
+- {Component 2}
+- {Component 3}
+
+**Actions:**
+- {Hành động 1} → {Kết quả}
+- {Hành động 2} → {Kết quả}
 
 <!-- Figma Design: {Link Figma — xóa dòng này nếu không có URL} -->
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anhth2/spec-driven-dev-plugin",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "AI-First Spec-Driven Development workflow plugin for Claude Code",
   "bin": {
     "spec-driven-dev": "./bin/index.js"
@@ -26,7 +26,14 @@
     "templates/",
     "ARCHITECTURE.md"
   ],
-  "keywords": ["claude-code", "spec-driven", "ai-first", "bdd", "traceability", "workflow"],
+  "keywords": [
+    "claude-code",
+    "spec-driven",
+    "ai-first",
+    "bdd",
+    "traceability",
+    "workflow"
+  ],
   "author": "Edupia Team",
   "license": "MIT",
   "repository": {

package/templates/prd.template.md

@@ -102,9 +102,9 @@
   - {Business value}→ Giá trị nghiệp vụ mang lại (lý do tại sao người dùng cần điều này)
 -->
 
-As a {User role}
-I want to {User goal}
-So that {Business value}
+- **As a** {User role}
+- **I want to** {User goal}
+- **So that** {Business value}
 
 ## b. Phạm vi
 
@@ -119,7 +119,8 @@ So that {Business value}
   - Viết ngắn gọn, súc tích, đủ để người đọc hiểu mà không cần giải thích thêm.
 -->
 
-In Scope
+**In Scope**
+
 - {Chức năng thuộc feature}
 
 ---
@@ -141,9 +142,9 @@ In Scope
   - Chi tiết kỹ thuật hoặc logic xử lý nội bộ → thuộc Business Rule / Business Logic.
 -->
 
-AC1: {Điều kiện chấp nhận}
-AC2: {Điều kiện chấp nhận}
-AC3: {Điều kiện chấp nhận}
+- **AC1:** {Điều kiện chấp nhận}
+- **AC2:** {Điều kiện chấp nhận}
+- **AC3:** {Điều kiện chấp nhận}
 
 ---
 
@@ -183,15 +184,24 @@ AC3: {Điều kiện chấp nhận}
 -->
 
 #### {TICKET_ID}-UC1: {Tên Use Case}
-Actor: {Người dùng thực hiện}
-Description: {Mô tả ngắn gọn kịch bản nghiệp vụ}
-Pre-condition: {Điều kiện cần trước khi Use Case bắt đầu}
-Post-condition: {Kết quả sau khi Use Case hoàn thành}
 
-Business Rule
-| ID | Business Rule | Business Logic |
-|----|---------------|----------------|
-| {TICKET_ID}-UC1-BR1 |               | - Logic 1<br/>- Logic 2<br/>- Logic 3 |
+- **Actor:** {Người dùng thực hiện}
+- **Description:** {Mô tả ngắn gọn kịch bản nghiệp vụ}
+- **Pre-condition:** {Điều kiện cần trước khi Use Case bắt đầu}
+- **Post-condition:** {Kết quả sau khi Use Case hoàn thành}
+
+**Business Rule**
+
+| ID | Business Rule |
+|----|---------------|
+| {TICKET_ID}-UC1-BR1 | |
+
+**Business Logic**
+
+**{TICKET_ID}-UC1-BR1:**
+- Logic 1
+- Logic 2
+- Logic 3
 
 ---
 
@@ -246,11 +256,16 @@ flowchart TD
 
 **Screen N: {Tên màn hình}**
 
-| Thành phần     | Chi tiết |
-| -------------- | -------- |
-| **Screen**     | {Tên màn hình} |
-| **Components** | - {Component 1} <br>- {Component 2} <br>- {Component 3} |
-| **Actions**    | - {Hành động 1} → {Kết quả} <br>- {Hành động 2} → {Kết quả} |
+**Screen:** {Tên màn hình}
+
+**Components:**
+- {Component 1}
+- {Component 2}
+- {Component 3}
+
+**Actions:**
+- {Hành động 1} → {Kết quả}
+- {Hành động 2} → {Kết quả}
 
 <!-- Figma Design: {Link Figma — xóa dòng này nếu không có URL} -->