@relipa/ai-flow-kit 0.1.4-beta.0 → 0.1.5-beta.0

package/custom/templates/shared/create-testcase-workflow.md

@@ -13,9 +13,9 @@ Các skill sau đây được cài tự động vào `.claude/skills/test-skills
 
 | Skill | File |
 |---|---|
-| `QA Writing Standards` | `.claude/skills/test-skills/rules/QA_Writing_Standards.md` |
-| `Directory & Naming Convention` | `.claude/skills/test-skills/rules/Directory_and_Naming_Convention.md` |
-| `Template TestCase` | `.claude/skills/test-skills/template/template_testcase.md` |
+| `QA Writing Standards` | `.claude/skills/test-skills/rules/qa-writing-standards.md` |
+| `Directory & Naming Convention` | `.claude/skills/test-skills/rules/directory-and-naming-convention.md` |
+| `Template TestCase` | `.claude/skills/test-skills/template/testcase-template.md` |
 | `00.01 Requirement Analysis` | `.claude/skills/test-skills/categories/00-core/00.01.requirement-analysis.md` |
 | `00.02 Risk Analysis` | `.claude/skills/test-skills/categories/00-core/00.02.risk-analysis.md` |
 | `00.03 Test Scenario Builder` | `.claude/skills/test-skills/categories/00-core/00.03.test-scenario-builder.md` |
@@ -46,40 +46,40 @@ Các skill sau đây được cài tự động vào `.claude/skills/test-skills
 ### Cấu trúc thư mục đầu ra
 
 ```
-docs/ak-{project}/testcase/
-├── Result/
-│   ├── [functionId]_01_Requirement_Analysis_Result.md     ← Gate 1 tạo
-│   ├── [functionId]_02_Test_Scenarios_Result.md           ← Gate 2 tạo
-│   ├── [functionId]_03_Test_Cases_Draft_Result.md         ← Gate 3 tạo
-│   └── [functionId]_04_Test_Cases_Final_Result.md         ← Gate 4 tạo (đồng thời với TestCase)
-├── QA/
-│   ├── [functionId]_01_Requirement_Analysis_QA.md         ← Gate 1 tạo (nếu có issue)
-│   ├── [functionId]_02_Scenario_Building_QA.md            ← Gate 2 tạo (nếu có issue)
-│   ├── [functionId]_03_Test_Design_QA.md                  ← Gate 3 tạo (nếu có issue)
-│   └── [functionId]_04_Test_Review_QA.md                  ← Gate 4 tạo
-└── TestCase/
-    └── [functionId]_TestCase.md                           ← Gate 4 tạo đồng thời với 04_Final_Result
+03.Testing/
+├── 01.Testcases/
+│   └── [functionId]/[functionId]_TestCase.md                  ← Gate 4 tạo
+└── 07.AI-Artifacts/
+    └── [functionId]/
+        ├── [functionId]_01_Requirement_Analysis_Result.md     ← Gate 1 tạo
+        ├── [functionId]_01_Requirement_Analysis_QA.md         ← Gate 1 tạo (nếu có issue)
+        ├── [functionId]_02_Test_Scenarios_Result.md           ← Gate 2 tạo
+        ├── [functionId]_02_Scenario_Building_QA.md            ← Gate 2 tạo (nếu có issue)
+        ├── [functionId]_03_Test_Cases_Draft_Result.md         ← Gate 3 tạo
+        ├── [functionId]_03_Test_Design_QA.md                  ← Gate 3 tạo (nếu có issue)
+        ├── [functionId]_04_Test_Cases_Final_Result.md         ← Gate 4 tạo (cùng TestCase)
+        └── [functionId]_04_Test_Review_QA.md                  ← Gate 4 tạo
 ```
 
-Ví dụ: `functionId = AD06`, `project = kcandy` → thư mục gốc là `docs/ak-kcandy/testcase/`
+Ví dụ: `functionId = AD06` → thư mục gốc là `03.Testing/`
 
 ---
 
 ### Quy trình tổng quan 4 Gates
 
 ```
-(testcase/ = docs/ak-{project}/testcase/ — viết tắt cho ngắn gọn)
+(AI-Artifacts/ = 03.Testing/07.AI-Artifacts/ — viết tắt cho ngắn gọn)
 
-[Input: SRS / Jira / Backlog / Spec file] → Pre-flight: xác định functionId + thư mục đầu ra
+[Input: SRS / Jira / Backlog / Spec file] → Pre-flight: BẮT BUỘC xác định functionId
     ↓
-Gate 1: Phân tích yêu cầu & Đánh giá rủi ro  → testcase/Result/ + testcase/QA/
+Gate 1: Phân tích yêu cầu & Đánh giá rủi ro  → AI-Artifacts/[functionId]/
     ↓ APPROVED
-Gate 2: Xây dựng Kịch bản (Scenario Building) → testcase/Result/ + testcase/QA/
+Gate 2: Xây dựng Kịch bản (Scenario Building) → AI-Artifacts/[functionId]/
     ↓ APPROVED
-Gate 3: Thiết kế Test Case chi tiết           → testcase/Result/ + testcase/QA/
+Gate 3: Thiết kế Test Case chi tiết           → AI-Artifacts/[functionId]/
     ↓ APPROVED
-Gate 4: Review & Tối ưu hóa                  → testcase/Result/ + testcase/QA/
-                                              + testcase/TestCase/[functionId]_TestCase.md
+Gate 4: Review & Tối ưu hóa                  → AI-Artifacts/[functionId]/
+                                              + 03.Testing/01.Testcases/[functionId]/[functionId]_TestCase.md
     ↓ APPROVED (Fully / Conditionally)
 Sẵn sàng thực thi kiểm thử
 ```
@@ -91,54 +91,44 @@ Sẵn sàng thực thi kiểm thử
 **Mục tiêu:** Tiếp nhận đầu vào, hiểu nghiệp vụ, xác định phạm vi kiểm thử, nhận diện rủi ro và phát hiện vấn đề cần làm rõ trước khi xây dựng kịch bản.
 
 **Đầu ra (Outputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_01_Requirement_Analysis_Result.md`
-- `docs/ak-{project}/testcase/QA/[functionId]_01_Requirement_Analysis_QA.md` (nếu có issue)
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_QA.md` (nếu có issue)
 
 **Bước thực hiện:**
 
 #### Bước 0: Pre-flight — Xác định functionId và thư mục đầu ra
 
-**Xác định `functionId`:**
+**Xác định `functionId` (BẮT BUỘC):**
 
 Kiểm tra theo thứ tự ưu tiên:
 1. Trường `functionId` hoặc `screenId` trong `.aiflow/context/current.json`
 2. Rút gọn từ `ticketId` — bỏ dấu gạch, giữ ký hiệu (ví dụ: `AD-06` → `AD06`)
-3. Nếu không tìm thấy → **hỏi QA ngay**:
+3. Nếu không tìm thấy → **BẮT BUỘC hỏi QA ngay**:
 
 ```
 Không tìm thấy functionId trong context.
 Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-LOGIN, PM-003):
 ```
 
-→ Đợi QA trả lời, ghi nhận giá trị, dùng cho toàn bộ workflow.
+→ Đợi QA trả lời, ghi nhận giá trị, dùng cho toàn bộ workflow. KHÔNG ĐƯỢC TIẾP TỤC NẾU CHƯA CÓ functionId.
 
-**Xác định `{project}` và thư mục đầu ra:**
+**Xác định thư mục đầu ra:**
 
-1. Lấy `{project}` theo thứ tự ưu tiên:
-   - Trường `project` trong `.aiflow/context/current.json`
-   - Tên thư mục gốc workspace (chuyển lowercase, thay space bằng `-`)
-
-2. Kiểm tra tồn tại thư mục `docs/ak-{project}/testcase/` trong root dự án:
+1. Kiểm tra tồn tại thư mục `03.Testing/` trong root dự án:
    - **Tìm thấy** → thông báo xác nhận:
      ```
-     ✓ Thư mục đầu ra: docs/ak-{project}/testcase/
+     ✓ Thư mục đầu ra: 03.Testing/
      ✓ functionId: [functionId]
      → Bắt đầu Gate 1...
      ```
-   - **Không tìm thấy** → **hỏi QA**:
-     ```
-     Không tìm thấy thư mục docs/ak-{project}/testcase/.
-     Tên project là gì? (ví dụ: kcandy, crm-app)
-     ```
-     → Nhận tên project từ QA → chuyển lowercase → tạo toàn bộ cây thư mục:
+   - **Không tìm thấy** → tạo toàn bộ cây thư mục:
      ```
-     docs/ak-{project}/testcase/Result/
-     docs/ak-{project}/testcase/QA/
-     docs/ak-{project}/testcase/TestCase/
+     03.Testing/01.Testcases/[functionId]/
+     03.Testing/07.AI-Artifacts/[functionId]/
      ```
      → Thông báo:
      ```
-     ✓ Đã tạo thư mục: docs/ak-{project}/testcase/
+     ✓ Đã tạo thư mục: 03.Testing/
      ✓ functionId: [functionId]
      → Bắt đầu Gate 1...
      ```
@@ -150,7 +140,7 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 - Nếu có file yêu cầu thô được chỉ định → đọc file đó
 
 #### Bước 2: Phân tích yêu cầu và đánh giá rủi ro
-- **READ skill:** `.claude/skills/test-skills/rules/QA_Writing_Standards.md` — đọc trước để nắm quy ước chung
+- **READ skill:** `.claude/skills/test-skills/rules/qa-writing-standards.md` — đọc trước để nắm quy ước chung
 - **READ skill:** `.claude/skills/test-skills/categories/00-core/00.01.requirement-analysis.md`
 - **READ skill:** `.claude/skills/test-skills/categories/00-core/00.02.risk-analysis.md`
 - Phân tích đầy đủ **16 mục** theo skill 00.01:
@@ -177,11 +167,11 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 
 #### Bước 3: Soạn thảo kết quả phân tích yêu cầu
 - Artifact đầu ra phải có: Feature Summary, Actor & Persona, Business Rules (16 mục), Risk Matrix, Test Scope
-- Lưu: `docs/ak-{project}/testcase/Result/[functionId]_01_Requirement_Analysis_Result.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_Result.md`
 
 #### Bước 4: Soạn thảo QA Artifact (nếu có issue)
 - Cấu trúc: Metadata, Detected Issues (Severity), Clarification Questions, Assumptions, Resolution Tracking
-- Lưu: `docs/ak-{project}/testcase/QA/[functionId]_01_Requirement_Analysis_QA.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_QA.md`
 
 #### Bước 5: Gate Review & Pause
 - **INVOKE** `gate-review` skill (generate mode) — ghi `.aiflow/review/gate-1-[functionId].md`
@@ -193,7 +183,7 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 → Nếu blocked: làm theo gate-review skill response protocol
 
 **Definition of Done:**
-- [ ] `functionId` và `{project}` đã được xác định, thư mục đầu ra đã sẵn sàng
+- [ ] `functionId` đã được xác định, thư mục đầu ra đã sẵn sàng
 - [ ] File `01_Requirement_Analysis_Result.md` có đủ 16 mục + Risk Matrix + Test Scope
 - [ ] File `01_Requirement_Analysis_QA.md` đã tạo nếu có issue (Critical/Major đã giải quyết)
 - [ ] Không có giả định nào được tự ý chốt thành fact mà không đưa vào QA
@@ -210,11 +200,11 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 **Điều kiện vào Gate 2:** Gate 1 đã **APPROVED** và `01_Requirement_Analysis_Result.md` đã hoàn chỉnh.
 
 **Đầu vào (Inputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_01_Requirement_Analysis_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_Result.md`
 
 **Đầu ra (Outputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_02_Test_Scenarios_Result.md`
-- `docs/ak-{project}/testcase/QA/[functionId]_02_Scenario_Building_QA.md` (nếu có issue)
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_02_Test_Scenarios_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_02_Scenario_Building_QA.md` (nếu có issue)
 
 **Bước thực hiện:**
 
@@ -245,10 +235,10 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
   - Cột: Scenario ID, Feature/Module, Check List, Scenario Type, Target Req ID, Priority, Test Data
 - Business Flow Mapping (E2E diagram dạng text)
 - Draft RTM (Scenario ID → Requirement ID từ `01_Requirement_Analysis_Result.md`)
-- Lưu: `docs/ak-{project}/testcase/Result/[functionId]_02_Test_Scenarios_Result.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_02_Test_Scenarios_Result.md`
 
 #### Bước 5: Soạn thảo QA Artifact (nếu có issue)
-- Lưu: `docs/ak-{project}/testcase/QA/[functionId]_02_Scenario_Building_QA.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_02_Scenario_Building_QA.md`
 - Minor issues → TBD marker + carry-forward, tiếp tục workflow
 
 #### Bước 6: Gate Review & Pause
@@ -279,18 +269,18 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 **Điều kiện vào Gate 3:** Gate 2 đã **APPROVED** và `02_Test_Scenarios_Result.md` đã hoàn chỉnh.
 
 **Đầu vào (Inputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_01_Requirement_Analysis_Result.md`
-- `docs/ak-{project}/testcase/Result/[functionId]_02_Test_Scenarios_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_02_Test_Scenarios_Result.md`
 
 **Đầu ra (Outputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_03_Test_Cases_Draft_Result.md`
-- `docs/ak-{project}/testcase/QA/[functionId]_03_Test_Design_QA.md` (nếu có issue)
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_03_Test_Cases_Draft_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_03_Test_Design_QA.md` (nếu có issue)
 
 **Bước thực hiện:**
 
 #### Bước 1: Đọc template và quy ước bắt buộc
-- **READ template:** `.claude/skills/test-skills/template/template_testcase.md` — **BẮT BUỘC** tuân thủ 100%
-- **READ skill:** `.claude/skills/test-skills/rules/QA_Writing_Standards.md`
+- **READ template:** `.claude/skills/test-skills/template/testcase-template.md` — **BẮT BUỘC** tuân thủ 100%
+- **READ skill:** `.claude/skills/test-skills/rules/qa-writing-standards.md`
 
 #### Bước 2: Áp dụng kỹ thuật thiết kế TC cơ bản (luôn áp dụng)
 - **READ:** `.claude/skills/test-skills/categories/01-test-design/01.01.boundary-value-analysis.md` — BVA cho tất cả trường số/text có giới hạn
@@ -329,10 +319,10 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
   - **Section 3.5**: Exceptions & Systems (Error Guessing cases)
 - Bổ sung: Coverage Matrix (Scenario ID → TC ID), Test Data tổng hợp
 - Ghi TBD marker khi thiếu thông tin: `[TBD — <issue-id>: mô tả ngắn]`
-- Lưu: `docs/ak-{project}/testcase/Result/[functionId]_03_Test_Cases_Draft_Result.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_03_Test_Cases_Draft_Result.md`
 
 #### Bước 7: Soạn thảo QA Artifact (nếu có issue)
-- Lưu: `docs/ak-{project}/testcase/QA/[functionId]_03_Test_Design_QA.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_03_Test_Design_QA.md`
 - Cấu trúc: Metadata, Detected Issues, Clarification Questions, Assumptions, Resolution Tracking
 
 #### Bước 8: Gate Review & Pause
@@ -345,7 +335,7 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 → Nếu blocked: làm theo gate-review skill response protocol
 
 **Definition of Done:**
-- [ ] 100% tuân thủ `template_testcase.md` — không tự định nghĩa cấu trúc mới
+- [ ] 100% tuân thủ `testcase-template.md` — không tự định nghĩa cấu trúc mới
 - [ ] Mọi trường input (cả Required và Optional) đã qua ma trận skill 02.02
 - [ ] TC Name section 3.3 bắt đầu bằng `"Kiểm tra trường [Tên Trường]..."`
 - [ ] Coverage Matrix mapping Scenario ID → TC ID đầy đủ
@@ -364,13 +354,13 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 **Điều kiện vào Gate 4:** Gate 3 đã **APPROVED** và `03_Test_Cases_Draft_Result.md` đã hoàn chỉnh.
 
 **Đầu vào (Inputs):**
-- `docs/ak-{project}/testcase/Result/[functionId]_01_Requirement_Analysis_Result.md`
-- `docs/ak-{project}/testcase/Result/[functionId]_03_Test_Cases_Draft_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_01_Requirement_Analysis_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_03_Test_Cases_Draft_Result.md`
 
 **Đầu ra (Outputs) — sinh ĐỒNG THỜI:**
-- `docs/ak-{project}/testcase/Result/[functionId]_04_Test_Cases_Final_Result.md`
-- `docs/ak-{project}/testcase/QA/[functionId]_04_Test_Review_QA.md`
-- `docs/ak-{project}/testcase/TestCase/[functionId]_TestCase.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_04_Test_Cases_Final_Result.md`
+- `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_04_Test_Review_QA.md`
+- `03.Testing/01.Testcases/[functionId]/[functionId]_TestCase.md`
 
 > **Quy tắc Gate 4:** Ba artifact trên phải được sinh ĐỒNG THỜI. Không tạo một file mà thiếu file kia.
 
@@ -401,19 +391,19 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
   - Final Test Cases (Approved, đã loại trùng và out-of-scope)
   - RTM Final (Req ID → Scenario ID → TC ID)
   - Sign-off Status (xem bảng bên dưới)
-- Lưu: `docs/ak-{project}/testcase/Result/[functionId]_04_Test_Cases_Final_Result.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_04_Test_Cases_Final_Result.md`
 
 #### Bước 4: Soạn thảo QA Artifact
 - Artifact `[functionId]_04_Test_Review_QA.md` gồm: Metadata, Findings, Issues, Sign-off Status
-- Lưu: `docs/ak-{project}/testcase/QA/[functionId]_04_Test_Review_QA.md`
+- Lưu: `03.Testing/07.AI-Artifacts/[functionId]/[functionId]_04_Test_Review_QA.md`
 
 #### Bước 5: Sinh TestCase Artifact — BẮT BUỘC đồng thời với Bước 3 & 4
-- Artifact `[functionId]_TestCase.md` theo `template_testcase.md` — **chỉ gồm:**
+- Artifact `[functionId]_TestCase.md` theo `testcase-template.md` — **chỉ gồm:**
   - **Mục 1**: Thông tin chung (điền functionId, ngày tạo)
   - **Mục 2**: Kết quả kiểm thử tổng hợp (reset về 0 chờ execution)
   - **Mục 3**: Danh sách Test Cases Chi Tiết (toàn bộ 5 sections đã Approved)
 - **KHÔNG chứa:** Review Summary, Findings, RTM, Coverage Matrix, Sign-off (thuộc `04_Final_Result.md`)
-- Lưu: `docs/ak-{project}/testcase/TestCase/[functionId]_TestCase.md`
+- Lưu: `03.Testing/01.Testcases/[functionId]/[functionId]_TestCase.md`
 
 #### Bước 6: Xác nhận Sign-off Status
 
@@ -451,7 +441,7 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 |---|---|---|
 | Gate 1 | `QA_Writing_Standards`, `00.01 Requirement Analysis`, `00.02 Risk Analysis` | `01_Requirement_Analysis_Result.md`, `01_QA.md` |
 | Gate 2 | `00.03 Scenario Builder`, `01.06 Error Guessing`, `03.02 Workflow Testing`, Domain skills | `02_Test_Scenarios_Result.md`, `02_QA.md` |
-| Gate 3 | `template_testcase`, `01.01 BVA`, `01.02 EP`, `01.03 Decision Table`, `01.06 Error Guessing`, `02.01`–`02.04`, `03.01`, `03.03`, `04.01`, `04.04` | `03_Test_Cases_Draft_Result.md`, `03_QA.md` |
+| Gate 3 | `testcase-template`, `01.01 BVA`, `01.02 EP`, `01.03 Decision Table`, `01.06 Error Guessing`, `02.01`–`02.04`, `03.01`, `03.03`, `04.01`, `04.04` | `03_Test_Cases_Draft_Result.md`, `03_QA.md` |
 | Gate 4 | `00.04 TC Review`, `99.01 Coverage Review` | `04_Final_Result.md`, `04_QA.md`, `[functionId]_TestCase.md` |
 
 ---
@@ -465,6 +455,6 @@ Vui lòng cung cấp mã định danh cho chức năng này (ví dụ: AD06, TC-
 - ✅ **BẮT BUỘC** chạy Bước 0 ở Gate 1 — xác nhận `functionId` và thư mục đầu ra trước khi làm bất cứ điều gì
 - ✅ **BẮT BUỘC** đọc skill từ `.claude/skills/test-skills/` — không suy luận từ bộ nhớ
 - ✅ **BẮT BUỘC** invoke `gate-review` cuối mỗi gate và chờ APPROVED
-- ✅ **BẮT BUỘC** tuân thủ 100% `template_testcase.md` ở Gate 3 và Gate 4
+- ✅ **BẮT BUỘC** tuân thủ 100% `testcase-template.md` ở Gate 3 và Gate 4
 - ✅ **BẮT BUỘC** ba artifact Gate 4 sinh ĐỒNG THỜI
 - ✅ **BẮT BUỘC** Issue Critical/Major phải giải quyết xong trước khi sinh Result artifact

package/custom/templates/shared/gate-workflow.md

@@ -50,7 +50,7 @@ AI actively reads ticket + source code to understand the requirement:
 → If passed: run `ak gate 1 approved --ticket [ticket-id]` → proceed to Gate 2
 → If blocked: follow gate-review skill response protocol
 
-> **Tip:** If auto-start doesn't trigger, the developer can start this gate by typing: **"start"**, **"Gate 1"** or **"Analyze ticket"**.
+> **Tip:** If auto-start doesn't trigger, the developer can start this gate by typing: **"start"**, **"Gate 1"** or **"Analyze ticket"**. If this chat session was already open when the ticket was loaded (`ak use`), those phrases won't mean anything to the AI yet since the `SessionStart` hook did not re-run — run **`/coding`** instead to load the ticket context manually.
 
 DO NOT just check format — **understand the content and propose solutions**.
 
@@ -357,7 +357,7 @@ Coverage: [N]% acceptance criteria
 
 ### GATE 1 — Pre-flight & Work Plan (auto-start)
 
-**INVOKE:** `execute-flow` skill (from `custom/skills/execute-flow/SKILL.md`)
+**INVOKE:** `execute-flow` skill (from `custom/skills/test-skills/execute-flow/SKILL.md`)
 
 Pre-flight checks (stop and report if any fail):
 0. **MCP Playwright is configured** — check `~/.claude/settings.json` (global user-level) for a `playwright` key in `mcpServers`. This is global — set once, works across all repos.
@@ -396,7 +396,7 @@ BASE_URL: [url]
 
 Only runs after Gate 1 APPROVED.
 
-**INVOKE:** `script-sync` skill (from `custom/skills/script-sync/SKILL.md`)
+**INVOKE:** `script-sync` skill (from `custom/skills/test-skills/script-sync/SKILL.md`)
 
 Hash-based TC↔script sync — for each TC in the file:
 - **New TC** (no matching `@tc-hash` in spec): generate Playwright test using MCP (`browser_navigate` → `browser_snapshot` → `browser_generate_locator`). Never fabricate selectors.

package/docs/common/CHANGELOG.md

@@ -7,6 +7,72 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [0.1.5] - 2026-07-01
+
+### Added
+
+- **Brainstorming Skill Integration** — Injected `superpowers:brainstorming` into Gate 1 of the BA Create Spec workflow, allowing the AI to actively clarify and brainstorm raw requirements from the backlog.
+- **Mandatory `functionId` Check** — Enforced mandatory `functionId` checks at Gate 1 of all BA and QA workflows (e.g., `create-spec-workflow.md`, `create-testcase-workflow.md`). If missing in the ticket or backlog description, the AI stops and prompts the user to input the ID.
+- **`/coding` slash command** — New `.claude/commands/coding.md`, installed alongside `/create-spec` and `/create-testcase`. Manually loads `.aiflow/context/current.json` and starts (or resumes) the `[DEV] 5-Gate Development Workflow` for `bug-fix` / `feature` / `refactor` / `investigation` / `documentation` tickets. Fixes a gap where those task types had no slash-command fallback: they relied solely on the `SessionStart` hook's auto-start message, which does not re-fire if a ticket is loaded with `ak use` while a Claude Code chat session is already open — leaving phrases like `"start"` with no effect since the AI was never given the ticket context. `ak use`'s "Next Steps" hint and the `gate-workflow.md` / `session-start.js` auto-start tips now also mention `/coding` as the manual fallback.
+
+### Changed
+
+- **Testing Skills Consolidation** — Consolidated all 11 testing/QA skills (previously at the root of `custom/skills/`) into the dedicated subfolder `custom/skills/test-skills/`. The skills moved are: `automation-testing`, `coverage-check`, `evidence-aggregation`, `execute-flow`, `generate-test-report`, `generate-testcase`, `log-bug`, `retest-orchestration`, `script-sync`, `test-analysis`, and `pr-impact-analysis`.
+- **English Kebab-Case Naming Standard** — Standardized all skill filenames in `custom/skills/ba-skills/` and `custom/skills/test-skills/` to use English kebab-case naming conventions.
+- **Output Directory Structure Migration** — Standardized output file templates, specs, and generated artifacts to use the new numbered directory architecture: `02.BA-Specs/`, `03.Testing/`, and `04.Coding/`.
+- **Removed Generic Testing Task Type** — Deprecated and removed the generic "Testing" task type from the CLI task selector (`scripts/use.js`) to enforce usage of the more specialized `testcase` and `execute` workflows.
+- **Reference Resolution** — Updated all hardcoded paths referencing relocated skills and output directories across `AIFLOW.md`, `CHANGELOG.md`, release notes, implementation plans, and gate workflow templates (`custom/templates/shared/gate-workflow.md`).
+- **Test Alignment** — Updated mock directory paths in the Jest test suite (`tests/review.test.js`) to align with the new `02.BA-Specs` directory structure.
+
+---
+
+## [0.1.4] - 2026-06-29
+
+### Added
+
+- **`spec` task type — 4-Gate BA Workflow (Create Spec)** — New end-to-end spec creation workflow for Business Analysts. Activated when `taskType: "spec"` in context. Orchestrated by the `create-spec` skill across 4 gates:
+  - **Gate 1 — Phân tích Yêu cầu Ban đầu**: AI reads ticket, classifies Facts vs Assumptions, identifies Gaps, generates a Q&A list for clarification. BA reviews → `APPROVED`.
+  - **Gate 2 — Q&A Loop & Confirm**: AI iterates through each Q&A answer, updates analysis until all items are Confirmed. BA approves full Q&A → `APPROVED`.
+  - **Gate 3 — Prototype Design**: AI generates HTML/CSS prototype for the main screens. BA reviews UI flow → `APPROVED`.
+  - **Gate 4 — UC Spec hoàn chỉnh**: AI produces a complete UC Spec document (flows, business rules, validations, edge cases). BA reviews → `APPROVED`.
+
+- **`testcase` task type — 4-Gate QA Workflow (Create Testcase)** — New structured test case creation workflow for QA engineers. Activated when `taskType: "testcase"` in context. Orchestrated by the `create-testcase` skill across 4 gates:
+  - **Gate 1 — Phân tích Yêu cầu & Rủi ro**: AI reads ticket/spec, analyzes scope and risk, reads source code to discover hidden validation rules and business logic. QA reviews → `APPROVED`.
+  - **Gate 2 — Xây dựng Scenarios & Checklist**: AI generates checklist grouped by Functional, Non-functional, Data & Integration, Regression. Checks Dev Artifacts (PR diff) via `pr-impact-analysis` skill to add regression TCs. Output: `test-plan/checklist.md`. QA reviews → `APPROVED`.
+  - **Gate 3 — Thiết kế Test Case chi tiết**: AI generates full TC table (TC_ID, Steps, Expected Result) using BVA, Equivalence Partitioning, Decision Table, State Transition techniques. Output: `test-plan/test-cases/`. QA reviews → `APPROVED`.
+  - **Gate 4 — Review & Tối ưu**: AI reviews coverage, removes duplicates, adds missing edge cases, exports final set to `test-plan/test-cases/final-testcases.md`. QA reviews → `APPROVED`.
+
+- **BA Skills Library** (`custom/skills/ba-skills/`) — New collection of BA-specific sub-skills:
+  - `skill-ba-phan-tich-ban-dau-v1` — Initial requirement analysis (Facts vs Assumptions, Gap Analysis)
+  - `skill-ba-qa-v1` — Q&A generation and confirmation loop
+  - `skill-ba-viet-spec-uc-v1` — UC Spec writing with flows, business rules, validations
+  - `skill-ba-prototype-v1` — HTML/CSS prototype generation for UI screens
+  - `skill-ba-ve-luong-mermaid-v1` — Mermaid flow diagram generation
+  - `skill-ba-xay-dung-business-rules-v1` — Business rules extraction and structuring
+
+- **Test Skills Library** (`custom/skills/test-skills/`) — New collection of 20+ QA sub-skills organized by category:
+  - **Core**: `requirement-analysis`, `risk-analysis`, `test-scenario-builder`, `testcase-review`
+  - **Test Design**: `boundary-value-analysis`, `equivalence-partitioning`, `decision-table`, `state-transition`, `pairwise`, `error-guessing`
+  - **UI Testing**: `UI-layout`, `form-validation`, `navigation`, `localization`, `accessibility`
+  - **Business Testing**: `CRUD-testing`, `workflow-testing`, `permission-testing`, `dependency-validation`, `notification-testing`, `calculation-testing`
+  - **Data Testing**: `database-testing`, `import-export-testing`, `data-mapping`, `duplicate-handling`, `migration`
+  - **Integration**: `API-testing`, `third-party-integration`, `batch-processing`, `file-upload-download`
+  - **Domain Skills**: `CMS`, `Ecommerce`
+  - **Review**: `coverage-review`, `knowledge-learning`, `repository-update`, `change-history`
+
+- **`gate-review` skill** (`custom/skills/gate-review/SKILL.md`) — New gate review orchestration skill that enforces explicit `APPROVED` at each gate boundary across all workflow types (coding, execute, spec, testcase). Prevents silent gate advancement without QA/BA/DEV sign-off.
+
+- **Gate review protocol in Execute Test Flow** — Gates 1, 3, and 4 of the execute-flow now explicitly require QA `APPROVED` before advancing. Gate 2 (Script Sync) is AI-only and advances automatically after sync completes.
+
+- **`spec` and `testcase` options in `ak use` type selector** — Both the `promptForTaskType()` shared function and the `manualContext()` flow now include `spec` and `testcase` as selectable types, routing AI to the correct 4-gate workflow.
+
+### Changed
+
+- **`aiflow` CLI alias fully deprecated → use `ak`** — All documentation, README, QUICK_START, cli-reference, and guide output updated to use `ak` as the primary command. The `aiflow` command still works but shows a deprecation warning on every invocation.
+- **README restructured** — "Overview Flow" section renamed to "Coding Flow"; Execute Test Flow merged into a single diagram (removed duplicate Vietnamese section); Create Spec Flow and Create Testcase Flow diagrams added.
+
+---
+
 ## [0.1.3] - 2026-06-18
 
 ### Added
@@ -17,11 +83,11 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   - **Gate 3 — Execute & Evidence**: Runs `npx playwright test` and organizes evidence into `ak-test/{repo}/results/{screenId}/run-{N}/` with per-TC folders (screenshots, trace.zip, result.md). Auto-drafts bug files for failed TCs. Supports `RETEST: [TC_ID]` loop.
   - **Gate 4 — Report & Bug Logging**: Generates `testreport.md` with Go/No-Go decision; logs each failed TC to Jira/Backlog one-by-one with interactive confirm per bug.
 
-- **`execute-flow` skill** (`custom/skills/execute-flow/SKILL.md`) — 4-gate execute flow orchestrator. Handles 3 entry points: `ak execute TICKET-ID` (ticket with `taskType: "execute"`), `ak execute ./path/to/testcases.md` (direct TC file), and `ak execute` (manual — AI asks for TC file). Output structure: `ak-test/{repo}/scripts/{screenId}/{ScreenID}.spec.ts` for scripts; `ak-test/{repo}/results/{screenId}/run-{N}/` for evidence.
+- **`execute-flow` skill** (`custom/skills/test-skills/execute-flow/SKILL.md`) — 4-gate execute flow orchestrator. Handles 3 entry points: `ak execute TICKET-ID` (ticket with `taskType: "execute"`), `ak execute ./path/to/testcases.md` (direct TC file), and `ak execute` (manual — AI asks for TC file). Output structure: `ak-test/{repo}/scripts/{screenId}/{ScreenID}.spec.ts` for scripts; `ak-test/{repo}/results/{screenId}/run-{N}/` for evidence.
 
-- **`script-sync` skill** (`custom/skills/script-sync/SKILL.md`) — Hash-based TC↔Playwright script sync engine. Called from execute-flow Gate 2. Never fabricates selectors — uses MCP browser tools (`browser_navigate` → `browser_snapshot` → `browser_generate_locator`) for any new/changed TC. Produces one `.spec.ts` per screen with all TCs inside, using `screenId` (lowercase) for directory paths and `{ScreenID}.spec.ts` (uppercase) for the filename.
+- **`script-sync` skill** (`custom/skills/test-skills/script-sync/SKILL.md`) — Hash-based TC↔Playwright script sync engine. Called from execute-flow Gate 2. Never fabricates selectors — uses MCP browser tools (`browser_navigate` → `browser_snapshot` → `browser_generate_locator`) for any new/changed TC. Produces one `.spec.ts` per screen with all TCs inside, using `screenId` (lowercase) for directory paths and `{ScreenID}.spec.ts` (uppercase) for the filename.
 
-- **`playwright.config.ts` template** for execute-flow (`custom/skills/execute-flow/templates/playwright.config.ts`) — Default config for each `ak-test/{repo}` repo with HTML + JSON reporters, screenshot-on-failure, and trace-on-failure. AI offers to scaffold this file during Gate 1 pre-flight if it doesn't exist.
+- **`playwright.config.ts` template** for execute-flow (`custom/skills/test-skills/execute-flow/templates/playwright.config.ts`) — Default config for each `ak-test/{repo}` repo with HTML + JSON reporters, screenshot-on-failure, and trace-on-failure. AI offers to scaffold this file during Gate 1 pre-flight if it doesn't exist.
 
 - **`execute` entry in `gate-workflow.md` Workflow Selection table** — `gate-workflow.md` (single source of truth for all AI agent instruction files) now routes `taskType: "execute"` to the `[EXECUTE] Executing Flow` section. Distributed to all agents (Claude, Gemini, Cursor, Copilot) via `ak init` / `ak up`.
 
@@ -29,17 +95,17 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 - **`ak execute` command** (`ak ex` alias) — New top-level CLI entry point that bypasses `ak use`. Accepts a ticket ID, a TC file path, or no argument (AI asks interactively). Documented in README, QUICK_START, cli-reference, and `ak guide --commands`.
 
-- **`test-analysis` skill** (`custom/skills/test-analysis/SKILL.md`) — Gate 1 analysis skill for the [TESTER] workflow. Reads ticket context, fetches linked docs, analyzes scope and risk, asks clarifying questions one at a time, and writes `test-plan/test-analysis.md`.
+- **`test-analysis` skill** (`custom/skills/test-skills/test-analysis/SKILL.md`) — Gate 1 analysis skill for the [TESTER] workflow. Reads ticket context, fetches linked docs, analyzes scope and risk, asks clarifying questions one at a time, and writes `test-plan/test-analysis.md`.
 
-- **`coverage-check` skill** (`custom/skills/coverage-check/SKILL.md`) — Gate 2d skill that applies review action items, generates a requirement→TC coverage matrix, exports the final test case set to `test-plan/test-cases/final-testcases.md`, and invokes `automation-testing` to generate Playwright scripts.
+- **`coverage-check` skill** (`custom/skills/test-skills/coverage-check/SKILL.md`) — Gate 2d skill that applies review action items, generates a requirement→TC coverage matrix, exports the final test case set to `test-plan/test-cases/final-testcases.md`, and invokes `automation-testing` to generate Playwright scripts.
 
-- **`evidence-aggregation` skill** (`custom/skills/evidence-aggregation/SKILL.md`) — Parses `test-results/results.json`, organizes screenshots and traces into `evidence/TC_[ID]-[scenario]/` folders, generates per-TC `result.md`, and auto-drafts `bugs/BUG-NNN-*.md` for failed TCs.
+- **`evidence-aggregation` skill** (`custom/skills/test-skills/evidence-aggregation/SKILL.md`) — Parses `test-results/results.json`, organizes screenshots and traces into `evidence/TC_[ID]-[scenario]/` folders, generates per-TC `result.md`, and auto-drafts `bugs/BUG-NNN-*.md` for failed TCs.
 
-- **`retest-orchestration` skill** (`custom/skills/retest-orchestration/SKILL.md`) — Handles the `RETEST: [TC_ID]` loop in Gate 3. Re-runs dev artifacts check (detect new commits), re-executes only specified TCs, creates `run-N/` subfolders (never deletes prior evidence), and updates bug status.
+- **`retest-orchestration` skill** (`custom/skills/test-skills/retest-orchestration/SKILL.md`) — Handles the `RETEST: [TC_ID]` loop in Gate 3. Re-runs dev artifacts check (detect new commits), re-executes only specified TCs, creates `run-N/` subfolders (never deletes prior evidence), and updates bug status.
 
-- **`pr-impact-analysis` skill** (`custom/skills/pr-impact-analysis/SKILL.md`) — Checks for new commits/PRs between gates to ensure TC coverage stays current with dev changes.
+- **`pr-impact-analysis` skill** (`custom/skills/test-skills/pr-impact-analysis/SKILL.md`) — Checks for new commits/PRs between gates to ensure TC coverage stays current with dev changes.
 
-- **`log-bug` skill** (`custom/skills/log-bug/SKILL.md`) — Logs a failed TC as a bug ticket in Jira/Backlog with structured fields (severity, steps, expected/actual, evidence link).
+- **`log-bug` skill** (`custom/skills/test-skills/log-bug/SKILL.md`) — Logs a failed TC as a bug ticket in Jira/Backlog with structured fields (severity, steps, expected/actual, evidence link).
 
 - **Playwright harness scaffold** — `ak scaffold playwright` (via `scripts/scaffold-playwright.js`) creates the `ak-test/{repo}/` directory structure with `playwright.config.ts`, `tests/e2e/fixtures/test.ts`, `tests/e2e/pages/BasePage.ts`, `tests/e2e/support/auth.ts`, and `.env.example`. Covered by 90-line Jest test suite in `tests/scaffold-playwright.test.js`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@relipa/ai-flow-kit",
-  "version": "0.1.4-beta.0",
+  "version": "0.1.5-beta.0",
   "description": "All-in-one AI Flow Kit for team development with Claude AI - skills, templates, and MCP adapters",
   "author": "Example Team",
   "publishConfig": {